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 13:25:00 -0000	[thread overview]
Message-ID: <bug-53455-4-OMegPbwioE@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 #15 from Niall Douglas <s_gccbugzilla at nedprod dot com> 2012-06-14 13:24:58 UTC ---
Agreed, but it is highly unlikely to happen anytime soon unless a new sponsor
turns up. BPL needs a fair bit of post-bitrot work as it is.

Niall

(In reply to comment #12)
> Maybe someone should look at fixing these warnings in Boost.Python, or ensure
> -fno-strict-aliasing is used
> 
>     "g++"  -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -m64
> -pthread -fPIC  -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG  -I"."
> -I"/apps/infra/3rd-party/gcc-4.4-64/python-2.6.5/include/python2.6" -c -o
> "bin.v2/libs/python/build/gcc-4.7.0/release/threading-multi/object/enum.o"
> "libs/python/src/object/enum.cpp"
> 
> libs/python/src/object/enum.cpp: In function 'boost::python::api::object
> boost::python::objects::{anonymous}::new_enum_type(const char*, const char*)':
> libs/python/src/object/enum.cpp:150:11: warning: dereferencing type-punned
> pointer will break strict-aliasing rules [-Wstrict-aliasing]
> 
>     "g++"  -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -m64
> -pthread -fPIC  -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG  -I"."
> -I"/apps/infra/3rd-party/gcc-4.4-64/python-2.6.5/include/python2.6" -c -o
> "bin.v2/libs/python/build/gcc-4.7.0/release/threading-multi/object/class.o"
> "libs/python/src/object/class.cpp"
> 
> libs/python/src/object/class.cpp: In function 'PyObject*
> boost::python::objects::static_data()':
> libs/python/src/object/class.cpp:211:11: warning: dereferencing type-punned
> pointer will break strict-aliasing rules [-Wstrict-aliasing]
> libs/python/src/object/class.cpp: In function 'boost::python::type_handle
> boost::python::objects::class_metatype()':
> libs/python/src/object/class.cpp:319:11: warning: dereferencing type-punned
> pointer will break strict-aliasing rules [-Wstrict-aliasing]
> libs/python/src/object/class.cpp: In function 'boost::python::type_handle
> boost::python::objects::class_type()':
> libs/python/src/object/class.cpp:473:11: warning: dereferencing type-punned
> pointer will break strict-aliasing rules [-Wstrict-aliasing]
> gcc.compile.c++
> bin.v2/libs/python/build/gcc-4.7.0/release/threading-multi/object/life_support.o
> 
>     "g++"  -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -m64
> -pthread -fPIC  -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG  -I"."
> -I"/apps/infra/3rd-party/gcc-4.4-64/python-2.6.5/include/python2.6" -c -o
> "bin.v2/libs/python/build/gcc-4.7.0/release/threading-multi/object/life_support.o"
> "libs/python/src/object/life_support.cpp"
> 
> libs/python/src/object/life_support.cpp: In function 'PyObject*
> boost::python::objects::make_nurse_and_patient(PyObject*, PyObject*)':
> libs/python/src/object/life_support.cpp:94:9: warning: dereferencing
> type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
> libs/python/src/object/life_support.cpp:96:9: warning: dereferencing
> type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
> gcc.compile.c++
> bin.v2/libs/python/build/gcc-4.7.0/release/threading-multi/object/function.o
> 
>     "g++"  -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -m64
> -pthread -fPIC  -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG  -I"."
> -I"/apps/infra/3rd-party/gcc-4.4-64/python-2.6.5/include/python2.6" -c -o
> "bin.v2/libs/python/build/gcc-4.7.0/release/threading-multi/object/function.o"
> "libs/python/src/object/function.cpp"
> 
> libs/python/src/object/function.cpp: In constructor
> 'boost::python::objects::function::function(const
> boost::python::objects::py_function&, const boost::python::detail::keyword*,
> unsigned int)':
> libs/python/src/object/function.cpp:108:9: warning: dereferencing type-punned
> pointer will break strict-aliasing rules [-Wstrict-aliasing]
> libs/python/src/object/function.cpp:110:9: warning: dereferencing type-punned
> pointer will break strict-aliasing rules [-Wstrict-aliasing]


  parent reply	other threads:[~2012-06-14 13:25 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
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 [this message]
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-OMegPbwioE@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).