Closed Bug 789753 Opened 7 years ago Closed 7 years ago

IonMonkey: Google's V8 test errors out on "Raytrace" on win64

Categories

(Core :: JavaScript Engine, defect)

18 Branch
x86_64
Windows 8
defect
Not set

Tracking

()

RESOLVED FIXED
mozilla18

People

(Reporter: pelpixanimations, Assigned: m_kato)

References

()

Details

(Whiteboard: [ion:p2])

Attachments

(2 files)

User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.8 (KHTML, like Gecko) Chrome/23.0.1255.0 Safari/537.8

Steps to reproduce:

Ran Google's V8 on the latest Ionmonkey nightly


Actual results:

the Raytraced scene was rendered incorrectly, and the test therefore failed.


Expected results:

It should have rendered properly, and did in the equivalent central build
Summary: ionmonkey → Google's V8 test errors out on "Raytrace" on the latest Ionmonkey nightly.
Summary: Google's V8 test errors out on "Raytrace" on the latest Ionmonkey nightly. → Google's V8 test errors out on "Raytrace" on the latest Ionmonkey nightly
Could you provide a link to the exact test?
Or, if you prefer, Mozilla's version of the test here:
http://dromaeo.com/?v8
http://octane-benchmark.googlecode.com/svn/latest/index.html
The same error happens on the successor to V8, Octane.
I can't reproduce this on OS X. Can you try a 32-bit build and see if that works for you? It may be a problem on Windows 64-bit only.

It would also be good if you could try with a clean profile, to rule out extensions, modified prefs etc. Thanks!
Summary: Google's V8 test errors out on "Raytrace" on the latest Ionmonkey nightly → Google's V8 test errors out on "Raytrace" on the latest Ionmonkey x86_64 nightly
As suggested, I tried.  Here's a list of results:

Central x86: Executed Properly
Central x86_64: Executed Properly
Ionmonkey x86: Executed Properly
Ionmonkey x86_64: Error present
Summary: Google's V8 test errors out on "Raytrace" on the latest Ionmonkey x86_64 nightly → IonMonkey: Google's V8 test errors out on "Raytrace" on win64
Whiteboard: [ion:p2]
Status: UNCONFIRMED → NEW
Ever confirmed: true
Thanks.  Sorry for specifying the platform but not the architecture.  Silly me.  I had a busy day today.
If there's anything else I can do to help, please let me know.
Blocks: 791505
checkNumber isn't often 2321 on Win64 ION.  So error occurs.  Even if this is on js shell (win64), it has same issue.
Assignee: general → m_kato
Attachment #667821 - Flags: review?(dvander)
Attachment #666458 - Flags: review?(dvander)
Comment on attachment 666458 [details] [diff] [review]
Part 1: Call check-raytrace.js many times

Review of attachment 666458 [details] [diff] [review]:
-----------------------------------------------------------------

r=me as long as this doesn't time-out :)
Attachment #666458 - Flags: review?(dvander) → review+
Comment on attachment 667821 [details] [diff] [review]
Part 2: Save non-volatile XMM registers on Win64 ABI

Review of attachment 667821 [details] [diff] [review]:
-----------------------------------------------------------------

Good catch, thank you for fixing this!
Attachment #667821 - Flags: review?(dvander) → review+
(In reply to David Anderson [:dvander] from comment #10)
> Comment on attachment 666458 [details] [diff] [review]
> Part 1: Call check-raytrace.js many times
> 
> Review of attachment 666458 [details] [diff] [review]:
> -----------------------------------------------------------------
> 
> r=me as long as this doesn't time-out :)

linxu32 debug is often timeout on tbpl.  I don't land this test.  (to reproduce this, we need over 100 calls for raytrace.js...)
https://hg.mozilla.org/integration/mozilla-inbound/rev/3ce909bed24a
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla18
https://hg.mozilla.org/mozilla-central/rev/3ce909bed24a
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.