public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fragabr at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/39869]  New: Firefox 3.0.9 compilation with gcc 4.4.0 (segfault)
Date: Thu, 23 Apr 2009 15:29:00 -0000	[thread overview]
Message-ID: <bug-39869-13376@http.gcc.gnu.org/bugzilla/> (raw)

I have a Athlon64 X2 (Linux 2.6.30-rc3) and I can compile Firefox 3.0.9 fine
with gcc 4.3.3, but if I use gcc 4.4.0 it segfaults. My default optimization is
-O3. If I reduce to -O2, Firefox starts, but with huge letters and windows...

So gcc 4.4.0 is generating bad code trying to compile Firefox 3.0.9, because
gcc 4.3.3 compiles it just fine.

I thought it was best to report it here because it seens to be a regression in
gcc 4.4.0. Thanks.


-- 
           Summary: Firefox 3.0.9 compilation with gcc 4.4.0 (segfault)
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: blocker
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: fragabr at gmail dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39869


             reply	other threads:[~2009-04-23 15:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 15:29 fragabr at gmail dot com [this message]
2009-04-23 15:31 ` [Bug middle-end/39869] " pinskia at gcc dot gnu dot org
2009-04-23 15:38 ` fragabr at gmail dot com
2009-04-23 15:44 ` paolo dot carlini at oracle dot com
2009-04-23 16:29 ` jakub at gcc dot gnu dot org
2009-04-23 16:51 ` fragabr at gmail dot com

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=bug-39869-13376@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).