From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4295 invoked by alias); 14 Jun 2012 11:49:17 -0000 Received: (qmail 4275 invoked by uid 22791); 14 Jun 2012 11:49:15 -0000 X-SWARE-Spam-Status: No, hits=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED,TW_PM X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 14 Jun 2012 11:49:03 +0000 From: "s_gccbugzilla at nedprod dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53455] boost::python segfault Date: Thu, 14 Jun 2012 11:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: s_gccbugzilla at nedprod dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 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 X-SW-Source: 2012-06/txt/msg00896.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53455 --- Comment #11 from Niall Douglas 2012-06-14 11:49:01 UTC --- (In reply to comment #9) > maybe related: https://svn.boost.org/trac/boost/ticket/6919 > Had similar crash issue. Though in my case (which may well be different from > the OP) rebuilding boost with new flags fixed it. > If OP posts crashtest.cpp source, I'll be happy to run it through. > Here's how I rebuilt the f17 rpms: > > # cat ~/.rpmrc > optflags: x86_64 -O2 -g -std=c++11 -fno-strict-aliasing > # rpmbuild --rebuild boost-1.48.0-11.fc17.src.rpm With respect to the Boost bugtracker, if this is an aliasing bug then it's a bug in Boost. Strict aliasing isn't an optional part of the ISO standard. They shouldn't have closed that issue because -fno-strict-aliasing "fixes" the bug on 4.7. Equally, it could still be that GCC 4.7 is performing an unsafe strict aliasing optimisation which it didn't do in 4.6. Weirdly the Boost bugtracker thinks the bug fixed in GCC 4.7, whereas this bug is about a 4.7 regression from 4.6. Niall