Closed
Bug 551173
Opened 14 years ago
Closed 14 years ago
SPARC failures in acceptance suite
Categories
(Tamarin Graveyard :: Baseline JIT (CodegenLIR), defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
flash10.1-sparc
People
(Reporter: brbaker, Assigned: leon.sha)
References
Details
Attachments
(2 files)
1.30 KB,
patch
|
dschaffe
:
review+
|
Details | Diff | Splinter Review |
1.63 KB,
patch
|
brbaker
:
review+
edwsmith
:
review+
|
Details | Diff | Splinter Review |
After spot merging the following nanojit change into tamarin (https://bugzilla.mozilla.org/attachment.cgi?id=428637), running acceptance has a couple of new failures. The following acceptance tests crash: ecma3/Statements/etry_007.abc e4x/XML/e13_4_2.abc e4x/XML/e13_4_4_18.abc e4x/XML/e13_4_4_19.abc e4x/XML/e13_4_4_23.abc e4x/XML/e13_4_4_3.abc dbx avmshell_d (dbx) run ecma3/Statements/etry_007.abc t@1 (l@1) signal SEGV (no mapping at the fault address) in avmplus::AvmCore::atomWriteBarrier at line 4377 in file "AvmCore.cpp" 4377 decr_atom(*address); All of the XML tests crash with this error, must have the JIT forced: (dbx) run -Ojit acceptance/e4x/XML/e13_4_2.abc t@1 (l@1) signal SEGV (no mapping at the fault address) in avmplus::ScopeChain::getSize at line 96 in file "ScopeChain-inlines.h" 96 return _scopeTraits->size; In /DEBUGGER/ builds the following fails: ecma3/Statements/block.abc (dbx) run ecma3/Statements/block.abc t@1 (l@1) signal SEGV (no mapping at the fault address) in avmplus::ScopeTypeChain::getScopeIsWithAt at line 67 in file "ScopeChain-inlines.h" 67 return (_scopes[i] & ISWITH) != 0;
Flags: flashplayer-triage+
Flags: flashplayer-qrb?
Updated•14 years ago
|
Assignee: nobody → leon.sha
Flags: flashplayer-qrb? → flashplayer-qrb+
Priority: -- → P1
Target Milestone: --- → flash10.1
These failures are caused by a compiler bug. The patch will come out in several weeks. I have an ugly workaround for this bug. I suggest we wait the compiler patch.
Reporter | ||
Comment 2•14 years ago
|
||
mark the failures on solaris SPARC as known until the compiler bug is fixed
Attachment #432179 -
Flags: review?(dschaffe)
Updated•14 years ago
|
Attachment #432179 -
Flags: review?(dschaffe) → review+
Targeting for 10.1.1.
Status: NEW → ASSIGNED
Target Milestone: flash10.1 → flash10.1.1
Reporter | ||
Comment 4•14 years ago
|
||
Need to rebase the known failures now that tr and tr-argo have anew nanojit. In the recent merge I know that at least one additional testcase is causing a core dump: ecma3/Date/e15_9_5_4.as
Reporter | ||
Comment 5•14 years ago
|
||
Submitted a new SPARC bug, #552650, it does not appear to be the same issue to me but cross commenting anyways.
Reporter | ||
Comment 7•14 years ago
|
||
from bug 552650 (In reply to comment #3) > I just confirmed, it is the same bug as bug 551173. In mozilla tree we use -xO2 > to compile Assembler.cpp instead of -xO5 as a workaround. I modified the configure script in tamarin to use -x02 on all files and was not able to workaround the problem.
Reporter | ||
Comment 8•14 years ago
|
||
Leon has there been any update on when a SunStudio compiler patch will be released that addresses this issue? SPARC compiling and testing has been offline for a long time and I am a little concerned.
The latest patch for sunstudio 12u1 didn't include the fix for this bug. Sorry for the wrong information. I post this patch to use -xO2 instead of -xO5 as a workaround. I guess last -x02 not working because "-xO2" should be used not "-x02". It is the difference between "0" and "O". Brent, can you try this patch and have a review? Thanks a lot.
Attachment #438652 -
Flags: review?(brbaker)
Reporter | ||
Comment 10•14 years ago
|
||
Comment on attachment 438652 [details] [diff] [review] Use -xO2 instead of -xO5 to workaround sunstudio 12u1 bugs. Looks good. Patch works in tamarin-redux. I have run most of the acceptance passes at this stage cleanly, will report back once they are all done. Hand applying the patch to tamarin-redux-argo does not fix the issue, I would guess that there are some necessary changes in tr that are not in tr-argo in order to get SPARC working. QRB: what is the solaris SPARC schedule for fp 10.1? I am guessing that there needs to be some back porting of nanojit changes into tamarin-redux-argo so that we can get SPARC working in that branch properly.
Attachment #438652 -
Flags: review?(brbaker) → review+
Reporter | ||
Updated•14 years ago
|
Flags: flashplayer-qrb+ → flashplayer-qrb?
Assignee | ||
Comment 11•14 years ago
|
||
http://hg.mozilla.org/tamarin-redux/rev/461cb64b9048
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 12•14 years ago
|
||
(In reply to comment #10) > Hand applying the patch to tamarin-redux-argo does not fix the issue, I would > guess that there are some necessary changes in tr that are not in tr-argo in > order to get SPARC working. I guess tamarin-redux-argo using different build system other that tamarin-redux.
Reporter | ||
Comment 13•14 years ago
|
||
(In reply to comment #12) > I guess tamarin-redux-argo using different build system other that > tamarin-redux. tr-argo and tr use the same build system, however tamarin-redux-argo version of nanojit is currently at the following revision: http://hg.mozilla.org/projects/nanojit-central/rev/3fa60904a28e So I am not sure if the issue in tr-argo is because SPARC compilation requires additional changes passed this nanojit rev. Will ping QRB directly about this issue.
Reporter | ||
Comment 14•14 years ago
|
||
Hi Brent, I have just try this tree. I applied the following three changesets. http://hg.mozilla.org/tamarin-redux/rev/461cb64b9048 http://hg.mozilla.org/tamarin-redux/rev/203096443c6f http://hg.mozilla.org/tamarin-redux/rev/8fa983fa3812 The acceptance test goes smoothly. Regards, Leon Sha Brent: I have confirmed that applying the above patches to tamarin-argo rev3974 will fix the SPARC shell and all acceptance runs pass (hybrid, interp, jit, debug, debugger, release etc). I am marking this issue as "REOPENED" until there is a decision from QRB about back porting this into argo QRB: I recommend that these changes be back ported from redux into the argo branch.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 15•14 years ago
|
||
recommend taking these changes to facilitate testing bug 558428
Blocks: 558428
Comment 16•14 years ago
|
||
Targeting for 10.1, requesting additional review by Edwin Smith.
Flags: flashplayer-qrb? → flashplayer-qrb+
Target Milestone: flash10.1.1 → flash10.1
Attachment #438652 -
Flags: review?(edwsmith)
Updated•14 years ago
|
Attachment #438652 -
Flags: review?(edwsmith) → review+
Reporter | ||
Comment 17•14 years ago
|
||
Patch pushed into tr-argo: 3983:13caa279c63a
Reporter | ||
Comment 18•14 years ago
|
||
Found 2 issues in the testsuite: debugger builds running the following testcases are EXTREMELY slow. I ended up killing the run after 5 minutes - as3/sampling/Callback.abc - as3/sampling/FunctionEntry.abc Callback does slowly spit out callback information, but after 5 minutes I stopped it, should run much faster -bash-3.00$ $AVM as3/sampling/Callback.abc Sampling api: callback callback1 called at 360 callback1 called at 394 callback1 called at 394 callback1 called at 394 callback1 called at 394 callback1 called at 394 callback1 called at 394 callback1 called at 394
Reporter | ||
Comment 19•14 years ago
|
||
There are also 3 failures in test/acceptance/spidermonkey/js1_5/Regress/regress-58116
Reporter | ||
Comment 20•14 years ago
|
||
Marked testcases as skip (sampling) and as expectedfail (spidermonkey) tr/tr-argo: 826390e43bfb tr only: 093e73b8f3be
Reporter | ||
Comment 21•14 years ago
|
||
(In reply to comment #19) > There are also 3 failures in > test/acceptance/spidermonkey/js1_5/Regress/regress-58116 These failures are tracked as bug #551227
Updated•14 years ago
|
Target Milestone: flash10.1 → flash10.1-Sparc
Comment 22•14 years ago
|
||
Brent, please verify and resolve. the slow debugger issue wa logged as bug 560536
Reporter | ||
Comment 23•14 years ago
|
||
Solaris buildslave is back online compiling and running acceptance suite. Marking as Verified/fixed Slow running tests are being skipped (tracked via 560536)
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Depends on: 560536
Resolution: --- → FIXED
Reporter | ||
Updated•14 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•