Bug 39869 - Firefox 3.0.9 compilation with gcc 4.4.0 (segfault)
Summary: Firefox 3.0.9 compilation with gcc 4.4.0 (segfault)
Status: RESOLVED INVALID
Alias: None
Product: gcc
Classification: Unclassified
Component: middle-end (show other bugs)
Version: 4.4.0
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords: wrong-code
Depends on:
Blocks:
 
Reported: 2009-04-23 15:29 UTC by Dâniel Fraga
Modified: 2009-04-23 16:50 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dâniel Fraga 2009-04-23 15:29:31 UTC 
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.
Comment 1 Andrew Pinski 2009-04-23 15:31:21 UTC 
We need more information than this.
Comment 2 Dâniel Fraga 2009-04-23 15:38:03 UTC 
What informa(In reply to comment #1)
> We need more information than this.

What information do you need? Couldn't you compile Firefox yourself to test it? Or if someone uses x86_64 I'm sure he/she will notice this.

Anyway just ask what you want. If I can provide, I'll reply as soon as possible. Thanks.
Comment 3 Paolo Carlini 2009-04-23 15:43:51 UTC 
See here:

  http://gcc.gnu.org/bugs.html#report
Comment 4 Jakub Jelinek 2009-04-23 16:29:16 UTC 
Likely related to https://bugzilla.redhat.com/show_bug.cgi?id=487844
which is a nspr bug.
Comment 5 Dâniel Fraga 2009-04-23 16:50:51 UTC 
(In reply to comment #4)
> Likely related to https://bugzilla.redhat.com/show_bug.cgi?id=487844
> which is a nspr bug.
> 

Ok, thanks. So I'm closing this bug.