RESOLVED FIXED43410
Enable JSValue32_64 on ARM by default 
https://bugs.webkit.org/show_bug.cgi?id=43410
Summary Enable JSValue32_64 on ARM by default
Gabor Loki
Reported 2010-08-03 04:22:24 PDT
The ARM_TRADITIONAL back-end should also follow the direction of JSValue development. Here is some performance numbers: SunSpider: sunspider-results-jsc-v7-jsvalue32_64.js : 2134.3 sunspider-results-jsc-v7-jsvalue32.js : 3886.1 (1.821x as slow) V8: sunspider-results-jsc-v7-jsvalue32.js : 14600.2 sunspider-results-jsc-v7-jsvalue32_64.js : 15961.8 (1.093x as slow) WindScorpion: sunspider-results-jsc-v7-jsv32_64.js : 9548.5 sunspider-results-jsc-v7-jsv32.js : 9662.75 (1.012x as slow) So, 2 of the 3 benchmark say the JSValue32_64 is faster. Although the r64319 or r64320 causes 10% performance regression in JSValue32 on ARM (see at http://webkit.sed.hu/benchmark/query/advanced/63695;64541;linux-arm-qt;jit;ss;speed ). So the overall picture is not so clear. ;)
Attachments
Enable JSValue32_64 on ARM by default (1.40 KB, patch)
2010-08-03 04:30 PDT, Gabor Loki 		loki: commit-queue-
DetailsFormatted DiffDiff
Enable JSValue32_64 for GCC on ARM by default (1.46 KB, patch)
2010-08-03 06:56 PDT, Gabor Loki 		ggaren: review+
loki: commit-queue-
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Gabor Loki
Comment 1 2010-08-03 04:30:32 PDT
Created attachment 63323 [details] Enable JSValue32_64 on ARM by default
Gabor Loki
Comment 2 2010-08-03 06:56:39 PDT
Created attachment 63332 [details] Enable JSValue32_64 for GCC on ARM by default Enable JSValue32_64 only for GCC on ARM. JSValue32_64 will be enabled for RVCT in another patch.
Geoffrey Garen
Comment 3 2010-08-03 11:05:29 PDT
Comment on attachment 63332 [details] Enable JSValue32_64 for GCC on ARM by default r=me
Gabor Loki
Comment 4 2010-08-04 00:45:00 PDT
Committed revision 64632.
Note You need to log in before you can comment on or make changes to this bug.