public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "maxime at altribe dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/44164] New: [4.5.0] Aliasing bug triggered by Boost.Bind/Boost.Function Date: Mon, 17 May 2010 08:28:00 -0000 [thread overview] Message-ID: <bug-44164-19190@http.gcc.gnu.org/bugzilla/> (raw) Using Boost.Bind/Boost.Function triggers what seems to be an aliasing bug with G++ 4.5.0. The minimal test case (including Boost.Bind and Boost.Function) is attached. It works and no errors are detected by valgrind with either flags : -O0 -O1 -O2 -fno-inline -O2 -fno-strict-aliasing -Os It crashes whith either flags and valgrind detects invalid reads : -02 -O3 Everything works fine with gcc version 4.4.3 20100316. There are no warnings using '-W -Wall -Wextra'. Original bug report to boost mailing list : http://lists.boost.org/boost-users/2010/05/59020.php -- Summary: [4.5.0] Aliasing bug triggered by Boost.Bind/Boost.Function Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: maxime at altribe dot org GCC build triplet: ../configure --prefix=/usr --enable- languages=c,c++,fortran,objc GCC host triplet: x86_64-unknown-linux-gnu GCC target triplet: x86_64-unknown-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44164
next reply other threads:[~2010-05-17 8:28 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-05-17 8:28 maxime at altribe dot org [this message] 2010-05-17 8:32 ` [Bug middle-end/44164] " maxime at altribe dot org 2010-05-17 9:39 ` [Bug middle-end/44164] [4.5 Regression] " rguenth at gcc dot gnu dot org 2010-05-17 9:44 ` rguenth at gcc dot gnu dot org 2010-05-17 13:10 ` maxime at altribe dot org 2010-05-17 15:50 ` rguenth at gcc dot gnu dot org 2010-05-17 15:58 ` rguenth at gcc dot gnu dot org 2010-05-17 19:11 ` pdimov at gmail dot com 2010-05-17 19:17 ` pinskia at gcc dot gnu dot org 2010-05-17 20:12 ` pdimov at gmail dot com 2010-05-18 14:58 ` rguenth at gcc dot gnu dot org 2010-05-18 15:01 ` rguenth at gcc dot gnu dot org 2010-05-18 15:02 ` [Bug c++/44164] " rguenth at gcc dot gnu dot org 2010-05-18 20:58 ` pluto at agmk dot net 2010-05-19 13:00 ` rguenth at gcc dot gnu dot org 2010-05-19 22:16 ` jason at gcc dot gnu dot org 2010-05-19 22:53 ` jason at gcc dot gnu dot org 2010-05-20 5:36 ` jason at gcc dot gnu dot org 2010-05-20 11:48 ` rguenther at suse dot de 2010-05-20 13:24 ` rguenth at gcc dot gnu dot org 2010-05-20 14:01 ` jason at gcc dot gnu dot org 2010-05-20 14:02 ` [Bug rtl-optimization/44164] " jason at gcc dot gnu dot org 2010-05-25 13:57 ` rguenth at gcc dot gnu dot org 2010-05-25 14:57 ` rguenth at gcc dot gnu dot org 2010-05-25 15:29 ` rguenth at gcc dot gnu dot org 2010-05-26 10:31 ` rguenth at gcc dot gnu dot org 2010-05-26 11:46 ` rguenth at gcc dot gnu dot org 2010-05-26 11:46 ` rguenth at gcc dot gnu dot org 2010-06-07 16:51 ` jamborm at gcc dot gnu dot org
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-44164-19190@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).