From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18479 invoked by alias); 14 Jan 2015 08:28:46 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 18421 invoked by uid 48); 14 Jan 2015 08:28:41 -0000 From: "jakub at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 4.9.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: WAITING X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-01/txt/msg01131.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64590 Jakub Jelinek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #10 from Jakub Jelinek --- 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.