From: Ryan Hill <dirtyepic@gentoo.org>
To: gcc@gcc.gnu.org
Subject: Re: gcc 4.7: -march=corei7-avx bug?
Date: Sun, 15 Apr 2012 09:24:00 -0000 [thread overview]
Message-ID: <20120415033320.6b599c2e@gentoo.org> (raw)
In-Reply-To: <jl14ea$t6j$1@dough.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 675 bytes --]
On Thu, 29 Mar 2012 04:53:45 -0300
Dâniel Fraga <fragabr@gmail.com> wrote:
> I tried to compile Firefox 11 with gcc 4.7 optimized with:
>
> -O3 -march=corei7-avx (I have a core i7 2700k)
>
> But Firefox segfaults (backtrace provided, although it seems
> not very useful):
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52762
>
> If I compile with -march=corei7 it runs perfectly.
>
> Maybe a gcc bug?
>
> How can I help you to debug this?
We've had to disable -mavx for firefox builds due to numerous issues like
this. Search the mozilla bugzilla for stack alignment issues.
--
fonts, gcc-porting
toolchain, wxwidgets
@ gentoo.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2012-04-15 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 7:54 Dâniel Fraga
2012-03-29 8:27 ` Jakub Jelinek
2012-03-29 17:43 ` Dâniel Fraga
2012-04-15 9:24 ` Ryan Hill [this message]
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=20120415033320.6b599c2e@gentoo.org \
--to=dirtyepic@gentoo.org \
--cc=gcc@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).