public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "s_gccbugzilla at nedprod dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53455] boost::python segfault
Date: Thu, 14 Jun 2012 11:49:00 -0000 [thread overview]
Message-ID: <bug-53455-4-x7XgCDvKvK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53455-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53455
--- Comment #11 from Niall Douglas <s_gccbugzilla at nedprod dot com> 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
next prev parent reply other threads:[~2012-06-14 11:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 17:41 [Bug c++/53455] New: g++ builds segfault in boost::python j.wielicki at sotecware dot net
2012-05-22 17:42 ` [Bug c++/53455] " j.wielicki at sotecware dot net
2012-05-22 17:50 ` j.wielicki at sotecware dot net
2012-05-22 18:36 ` s_gccbugzilla at nedprod dot com
2012-05-22 19:08 ` rene.kuettner at gmail dot com
2012-05-22 20:08 ` [Bug c++/53455] boost::python segfault s_gccbugzilla at nedprod dot com
2012-05-24 14:29 ` ndbecker2 at gmail dot com
2012-05-24 14:42 ` org.gnu.gcc.bugtracker at sotecware dot net
2012-05-24 15:10 ` org.gnu.gcc.bugtracker at sotecware dot net
2012-06-13 22:14 ` mbec at gmto dot org
2012-06-14 0:47 ` mbec at gmto dot org
2012-06-14 11:49 ` s_gccbugzilla at nedprod dot com [this message]
2012-06-14 12:51 ` redi at gcc dot gnu.org
2012-06-14 13:15 ` redi at gcc dot gnu.org
2012-06-14 13:22 ` redi at gcc dot gnu.org
2012-06-14 13:25 ` s_gccbugzilla at nedprod dot com
2012-06-14 13:27 ` org.gnu.gcc.bugtracker at sotecware dot net
2012-06-14 14:01 ` redi at gcc dot gnu.org
2012-06-14 15:15 ` s_gccbugzilla at nedprod dot com
2012-06-14 15:21 ` org.gnu.gcc.bugtracker at sotecware dot net
2012-06-14 15:45 ` redi at gcc dot gnu.org
2012-06-14 16:10 ` org.gnu.gcc.bugtracker at sotecware dot net
2012-06-14 16:16 ` s_gccbugzilla at nedprod dot com
2012-06-14 16:22 ` redi at gcc dot gnu.org
2012-06-14 16:24 ` redi at gcc dot gnu.org
2012-06-14 16:37 ` s_gccbugzilla at nedprod 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-53455-4-x7XgCDvKvK@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).