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++/52762] Firefox 11 segfault with gcc 4.7 (-O3 -march=corei7-avx)
Date: Fri, 30 Mar 2012 19:56:00 -0000 [thread overview]
Message-ID: <bug-52762-4-1IljoyQFD3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52762-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52762
--- Comment #8 from Dâniel Fraga <fragabr at gmail dot com> 2012-03-30 19:54:47 UTC ---
(In reply to comment #7)
> Happens in java script, which does JITed code.
> My guess is that one of the transition points between JITed code and C code
> does not save AVX registers correctly or something like that.
> I would file it with mozilla.org, it's more likely their bug.
Thanks Andi. I already had filled a bug in mozilla bugzilla. But unfortunatelly
nobody answered. I'll wait. Thanks.
Ps: should I mark this bug as "invalid"?
next prev parent reply other threads:[~2012-03-30 19:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 7:10 [Bug c++/52762] New: " fragabr at gmail dot com
2012-03-29 8:27 ` [Bug c++/52762] " markus at trippelsdorf dot de
2012-03-29 17:41 ` fragabr at gmail dot com
2012-03-29 18:10 ` fragabr at gmail dot com
2012-03-29 19:13 ` fragabr at gmail dot com
2012-03-29 19:17 ` markus at trippelsdorf dot de
2012-03-29 21:01 ` fragabr at gmail dot com
2012-03-30 19:23 ` andi-gcc at firstfloor dot org
2012-03-30 19:56 ` fragabr at gmail dot com [this message]
2012-04-04 15:51 ` jason at gcc dot gnu.org
2013-06-15 0:26 ` paolo.carlini at oracle 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-52762-4-1IljoyQFD3@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).