search

pingjiang / octane-benchmark

Automatically exported from code.google.com/p/octane-benchmark
0 stars 0 forks source link

V8's "shell" binary fails to load('pdfjs.js'); must use "d8" version #10

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. build both v8 shell binaries for your system
2. run octane with the shell version - "shell run.js"

What is the expected output? What do you see instead?
Expected (which I see using d8)...
Richards: 12465
DeltaBlue: 14943
Crypto: 16186
RayTrace: 15450
EarleyBoyer: 23748
RegExp: 3490
Splay: 5101
NavierStokes: 18642
PdfJS: 12069
Mandreel: 13183
Gameboy: 13953
CodeLoad: 15532
Box2D: 13448
----
Score (version 8): 12437

Actual result...
run.js:38: Error executing file
load('pdfjs.js');
^

What version of the product are you using? On what operating system?
v1 I think, but it was the trunk version from SVN today.  svn info says 
revision 22.  This is on an Xubuntu 12.10 x64 machine.  The shell version was 
3.16.3.1, but it also happens on 3.15.11.5.  And the shell fails in a 3.14 and 
3.13 version I have...but I don't have d8 for those handy.

Please provide any additional information below.
We've run v8 like this using the "shell" version and it worked fine.  We didn't 
plan to debug anything so the simpler executable seemed like a better choice.

Original issue reported on code.google.com by jmillenb...@nvidia.com on 25 Feb 2013 at 8:26

GoogleCodeExporter commented 9 years ago 
This is working as intended. The v8 shell you are talking about has been 
retired as primary testing platform more than a year ago and replaced by d8. 
It's meant as a sample (thus in the sample folder) and therefore some features 
that d8 provides are missing.

There should be no difference between d8 and the sample shell wrt performance.

Original comment by yangguo@chromium.org on 27 Feb 2013 at 8:30

GoogleCodeExporter commented 9 years ago 
In particular, it doesn't have any support for WebGL typed arrays, so can't run 
most of the new benchmarks.

Original comment by rossb...@chromium.org on 27 Feb 2013 at 8:36

GoogleCodeExporter commented 9 years ago 
Ah...I was working from previous people's efforts and they'd had me use that 
binary.  Also when I perform a build "shell" just ended up in the same location 
that "d8" did, so I didn't realize it was only a sample.

Thanks for the complete explanation.  We'll switch over to using "d8" instead.

Original comment by jmillenb...@gmail.com on 27 Feb 2013 at 7:10