Status: Accepted
Owner: [email protected]
CC: [email protected], [email protected], [email protected],
[email protected]
Labels: Type-Bug Priority-Medium
New issue 3263 by [email protected]: ARM64: V8 fails to run Octane.
http://code.google.com/p/v8/issues/detail?id=3263
When running the whole Octane (r33) suite, d8 will crash well into the
tests. Currently, this occurs in mandreel, but mandreel runs fine by
itself. I have also reproduced it in typescript when only zlib and
typescript are enabled.
On hardware, the crash looks like a seg. fault on a store instruction at
the end of a read-modify-write sequence in
CheckNeedsToInformIncrementalMarker. However, the address _is_ accessible;
the read worked, and GDB can access the memory. According to GDB, the value
in the location is corrupted at the start of this sequence. On hardware,
this failure only occurs on a release build.
In the arm64 simulator, I can also reproduce the crash on an optdebug
build, though the details seem to change from one run to the next.
I haven't ruled out the possibility that GDB is confused about the exact
details of the crash. Also, there may be more than one problem here. (Using
Valgrind, I've already noticed one problem, but it doesn't seem to be
related.)
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
