public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dbaron@fas.harvard.edu
To: gcc-gnats@gcc.gnu.org
Subject: optimization/2917: mozilla doesn't run with "-O2 -march=pentiumpro"
Date: Wed, 23 May 2001 19:26:00 -0000	[thread overview]
Message-ID: <20010524021917.27556.qmail@sourceware.cygnus.com> (raw)

>Number:         2917
>Category:       optimization
>Synopsis:       mozilla doesn't run with "-O2 -march=pentiumpro"
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Wed May 23 19:26:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     dbaron@fas.harvard.edu
>Release:        gcc 3.0 prerelease, various dates (see below)
>Organization:
>Environment:
RedHat 7.0+errata, dual P-733.
>Description:
See http://bugzilla.mozilla.org/show_bug.cgi?id=76604 for more information.

Sorry this bug doesn't have all the details it should have -- it may be very difficult to reduce down to something simple and I don't have time to reduce it.  (I haven't even had time to narrow down further when it started and which optimization levels it happens on, or keep up with testing that it still occurs on current snapshots.)

What I do know is this:
On gcc 3.0 prerelease snapshots from March 12 and earlier, mozilla compiled both without optimization (and with -g) and with optimization options "-O2 -march=pentiumpro" (and without -g).

On gcc 3.0 snapshots from March 26, April 2, April 9, April 16, and I think I tested April 30 (I didn't get a chance to try newer snapshots yet, although I'm building the May 21 snapshot now), the build without optimization still works but the build with optimization crashes.

I've found some slight changes to code that fix the crash, that are described in the URL above (the bugzilla bug report), but I'm not sure how helpful that is.

At one point I looked at the differences between the generated assembly between the March 12 and March 26 compilers, and some of the major differences seemed to be related to changes allowing inlining of static functions (changes that I think were made due to Mozilla's extensive use of them for retrieving IIDs).

Sorry for the lack of information here, but I decided to just file this bug rather than keep putting it off for lack of information that I'm only slowly finding the time to gather.  I really would like to see Mozilla be able to build with gcc3.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-05-23 19:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-23 19:26 dbaron [this message]
2001-08-13 16:01 rodrigc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010524021917.27556.qmail@sourceware.cygnus.com \
    --to=dbaron@fas.harvard.edu \
    --cc=gcc-gnats@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).