public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/38477] [strict-aliasing] warning message contains compiler-generated symbols Date: Tue, 13 Jan 2009 11:03:00 -0000 [thread overview] Message-ID: <20090113110307.31342.qmail@sourceware.org> (raw) In-Reply-To: <bug-38477-16067@http.gcc.gnu.org/bugzilla/> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 940 bytes --] ------- Comment #15 from rguenth at gcc dot gnu dot org 2009-01-13 11:03 ------- Smaller testcase for the possible libstdc++ / C++ FE issue, build with -O2 -finline-functions -Wstrict-aliasing -Wsystem-headers #include <set> class test { test(); void bar(int ci); std::set<int> foo; }; void test::bar(int ci ) { test ctx; ctx.foo.insert( ci ); } /usr/include/c++/4.4/bits/stl_function.h: In member function void test::bar(int): /usr/include/c++/4.4/bits/stl_function.h:230: warning: dereferencing pointer __x.13 does break strict-aliasing rules /usr/include/c++/4.4/bits/stl_tree.h:530: note: initialized from here /usr/include/c++/4.4/bits/stl_function.h:230: warning: dereferencing pointer __x.13 does break strict-aliasing rules /usr/include/c++/4.4/bits/stl_tree.h:530: note: initialized from here I am now trying to investigate who is at fault. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38477
next prev parent reply other threads:[~2009-01-13 11:03 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-12-10 17:17 [Bug c++/38477] New: " dimhen at gmail dot com 2008-12-10 17:40 ` [Bug libstdc++/38477] " rguenth at gcc dot gnu dot org 2008-12-10 17:46 ` rguenth at gcc dot gnu dot org 2008-12-12 11:11 ` paolo dot carlini at oracle dot com 2008-12-12 11:25 ` rguenth at gcc dot gnu dot org 2008-12-12 11:40 ` paolo dot carlini at oracle dot com 2008-12-12 11:45 ` rguenth at gcc dot gnu dot org 2008-12-12 11:54 ` paolo dot carlini at oracle dot com 2008-12-12 11:58 ` rguenth at gcc dot gnu dot org 2008-12-12 12:10 ` rguenth at gcc dot gnu dot org 2009-01-05 23:47 ` bkoz at gcc dot gnu dot org 2009-01-06 19:45 ` rguenth at gcc dot gnu dot org 2009-01-12 14:26 ` rguenth at gcc dot gnu dot org 2009-01-12 14:43 ` pluto at agmk dot net 2009-01-12 14:52 ` rguenth at gcc dot gnu dot org 2009-01-13 11:03 ` rguenth at gcc dot gnu dot org [this message] 2009-01-13 12:14 ` rguenth at gcc dot gnu dot org 2009-01-14 16:45 ` [Bug middle-end/38477] " rguenth at gcc dot gnu dot org 2009-01-14 16:47 ` rguenth 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=20090113110307.31342.qmail@sourceware.org \ --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).