public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/64590] Firefox 34 triggers GCC AVX bug (segfault: XPCCallContext::GetJSContext (this=0xfffc7fffe3e23980)) Date: Wed, 14 Jan 2015 08:28:00 -0000 [thread overview] Message-ID: <bug-64590-4-PInQuQJh9O@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64590-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64590 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> --- That most likely means a failed assertion implemented on the mozilla side as store to NULL pointer followed to __builtin_trap () just in case. Anyway, that doesn't look like a reason for the -march=nehalem vs. -march=sandybridge differences. If that really turns a working binary into non-working, perhaps try to bisect between -march=nehalem -O3 and -march=sandybridge -O3 (forget about -floop-interchange -floop-strip-mine -floop-block everywhere) built *.o files, until you find the problematic one. Then using __attribute__((target ("march=sandybridge"))) in -march=nehalem compiled object (or vice versa) you could try to bisect between different routines to find out where the problem is.
next prev parent reply other threads:[~2015-01-14 8:28 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-13 23:44 [Bug tree-optimization/64590] New: " fragabr at gmail dot com 2015-01-13 23:58 ` [Bug tree-optimization/64590] " pinskia at gcc dot gnu.org 2015-01-13 23:59 ` pinskia at gcc dot gnu.org 2015-01-14 2:19 ` fragabr at gmail dot com 2015-01-14 8:28 ` jakub at gcc dot gnu.org [this message] 2015-02-10 9:34 ` fragabr at gmail dot com 2015-02-11 5:31 ` dbaron at dbaron dot org 2015-02-11 11:06 ` 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-64590-4-PInQuQJh9O@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: linkBe 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).