Closed Bug 62719 Opened 24 years ago Closed 15 years ago

highly "optimized" Mozilla build with gcc fails to start

Categories

(SeaMonkey :: Build Config, defect)

Product:
SeaMonkey
Component:
Build Config
Platform:
Sun
Solaris
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: roland.mainz, Assigned: roland.mainz)

Details

Mozilla 2000-12-06-08-Mtrunk build with
% gcc -v
Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.7/2.95.1/specs
gcc version 2.95.1 19990816 (release)
% export CFLAGS="-O3 -fexpensive-optimizations -mv8"
% export CXXFLAGS="-O3 -fexpensive-optimizations -mv8"
% ../configure --with-xprint --enable-mathml --enable-svg --enable-xsl
--with-extensions
% make

failes like this:
-- snip --
% ./mozilla
# blah-blah
ARNING: waaah!, file ../../../../rdf/content/src/nsXULPrototypeDocument.cpp,
line 523
JavaScript strict warning: 
chrome://communicator/content/profile/confirmMigration.js line 51: function
onLoad does not always return a value
Note: frameverifytree is disabled
Assertion failure: ov != nv, at ../../../js/src/jslock.c:122
Abort - core dumped
-- snip --

GDB stack trace:
-- snip --
(gdb) where
#0  0xfece9d88 in __sigprocmask () from /usr/lib/libthread.so.1
#1  0xfecdf3e8 in _resetsig () from /usr/lib/libthread.so.1
#2  0xfecdeb34 in _sigon () from /usr/lib/libthread.so.1
#3  0xfece1a10 in _thrp_kill () from /usr/lib/libthread.so.1
#4  0xfec39470 in abort () from /usr/lib/libc.so.1
#5  0xff085f64 in Letext () at ../../../js/src/jsutil.c:174
-- snip --

Sure... a compiler issue... but is there a way to squish more out of the code
without running into these problems (well... Solaris has the famous(&much
better) Workshop compiler... which unfortunalty does not work (WS6, see bug
21138) ?
Update:
Tested various optimizer options...
Optimizer options                 |Result
----------------------------------+--------
-O3 -fexpensive-optimizations -mv8|coredump
-O3                               |coredump
-O2                               | working
-O                                | working

Setting milestones to Future.
Need stack traces from the coredumps.
Target Milestone: --- → Future
Summary: highly "optimized" Mozilla build with gcc failes to start → highly "optimized" Mozilla build with gcc fails to start
> Need stack traces from the coredumps.

Will file them in one or two weeks. Currently working on Xprint using Sun
Workshop 6U2EA. If those issues have been cleaned-up I file some stack traces
from gcc builds optimized to death... =:-)
Wortksforme. -O3 -march=i586
To Danny Colascion:
- This bug may be Solaris/SPARC-only
- It sometimes _works_, sometimes _not_. It even work on one machine and fails
on another... ;-(
WFM (linux, gcc-2.96-96, mozilla-cvs-20011121)
darin:
WFM-on-x86 is (unfortunately) not equal to WFM-on-SPARC. gcc on x86 seems to
work better than the SPARC port... ;-(
--> Roland
Assignee: cls → Roland.Mainz
Priority: P3 → --
Target Milestone: Future → ---
Reporter, do you still see this problem with the gcc 3.x on the latest nightly?
If not, this bug can be closed. Thanks.
Product: Browser → Seamonkey
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
I don't think we'll look into this any more, at least not specifically for SeaMonkey.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.