Last Comment Bug 507231 - ABORT_IF_XML does not guarantee no XML at runtime
: ABORT_IF_XML does not guarantee no XML at runtime
Status: RESOLVED INVALID
:
Product: Core
Classification: Components
Component: JavaScript Engine (show other bugs)
: Other Branch
: All All
: -- normal (vote)
: ---
Assigned To: general
:
:
Mentors:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-29 13:56 PDT by Jason Orendorff [:jorendorff]
Modified: 2013-02-21 12:11 PST (History)
5 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

Description Jason Orendorff [:jorendorff] 2009-07-29 13:56:59 PDT
As a result, XML objects can end up being treated like regular old objects in several places. This test passes without -j, fails with -j.

var arr = [{}, {},
           {}, {},
           {}, {},
           {}, {},
           <x/>, <x/>];  // these last two are equal
var s = '';
for (var i = 0; i < arr.length; i += 2) {
    if (arr[i] == arr[i + 1])
        s += i;
}
assertEq(s, "8");  // got "", expected "8" with -j
Comment 1 Jason Orendorff [:jorendorff] 2009-07-29 14:00:13 PDT
We could have ABORT_IF_XML emit a guard. That seems heinous. We could split XML objects out into their own trace type, TT_XML. But that might be even worse; we would pay for that every time we unbox an object on trace.
Comment 2 AWAY Tom Schuster [:evilpie] 2013-02-21 12:05:55 PST
E4X is gone.

Note You need to log in before you can comment on or make changes to this bug.