Closed
Bug 571698
Opened 14 years ago
Closed 14 years ago
TM: turn off int/double speculation when we record many peer trees
Categories
(Core :: JavaScript Engine, defect, P2)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
blocking2.0 | --- | betaN+ |
People
(Reporter: gal, Assigned: gal)
References
Details
Attachments
(1 file, 1 obsolete file)
28.62 KB,
patch
|
dvander
:
review+
|
Details | Diff | Splinter Review |
Right before we are about to blacklist a tree, switch of int/double speculation as a last resort. This fixes the issues vlad was seening with the darkroom demo.
Assignee | ||
Comment 1•14 years ago
|
||
Assignee: general → gal
Assignee | ||
Updated•14 years ago
|
Attachment #450869 -
Flags: review?(dvander)
Assignee | ||
Updated•14 years ago
|
blocking2.0: --- → ?
OS: Mac OS X → All
Priority: -- → P2
Hardware: x86 → All
Uhm, is checking for NULL "this" portable/valid?
Assignee | ||
Comment 3•14 years ago
|
||
Note sure. Let's ask someone who probably knows. Luke?
Comment 4•14 years ago
|
||
Wow, +1 for creativity. As far as portability/validity, while it is valid to be executing in the member function of an invalid object (which we do in TraceRecorder on a deep abort), 5.2.5 clause 3 says A->B is defined to be equivalent to (*(A)).B, and 8.3.2 clause 4 says there shall be no null references, so it seems that the act of calling a member function where the receiver is null results in undefined behavior. Practically speaking, this may justify the compiler in hoisting loads of member variables above the "if (this == NULL)" guard. So I'd shy away from this trick.
Assignee | ||
Comment 5•14 years ago
|
||
Alright. New patch in a few.
Assignee | ||
Comment 6•14 years ago
|
||
Attachment #450869 -
Attachment is obsolete: true
Attachment #450869 -
Flags: review?(dvander)
Assignee | ||
Updated•14 years ago
|
Attachment #450906 -
Flags: review?(dvander)
Updated•14 years ago
|
Attachment #450906 -
Flags: review?(dvander) → review+
Comment 7•14 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/66d75f2240b0
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 8•14 years ago
|
||
Thanks sayrer.
Updated•14 years ago
|
blocking2.0: ? → betaN+
You need to log in
before you can comment on or make changes to this bug.
Description
•