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 c++/42032] Aliasing errors in stl_tree.h Date: Fri, 13 Nov 2009 20:03:00 -0000 [thread overview] Message-ID: <20091113200258.32351.qmail@sourceware.org> (raw) In-Reply-To: <bug-42032-18432@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from rguenth at gcc dot gnu dot org 2009-11-13 20:02 ------- There are definitely a lot of casts like static_cast<_Link_type>(_M_node) in stl_list.h. If _M_node is ever not a rb_tree_node but only a rb_tree_node_base (which probably is the case again for the head of the tree) then this is an alias violation. Note that 4.5 will no longer warn for this because I removed the warning code as it wasn't aware of the concept of C++ dynamic types and thus lead to many false positives. There is no replacement for it, so you'll need to do code review to catch all cases. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42032
next prev parent reply other threads:[~2009-11-13 20:03 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-11-13 19:23 [Bug c++/42032] New: " craig dot schlenter at gmail dot com 2009-11-13 19:25 ` [Bug c++/42032] " pinskia at gcc dot gnu dot org 2009-11-13 19:34 ` craig dot schlenter at gmail dot com 2009-11-13 19:49 ` evan at chromium dot org 2009-11-13 19:54 ` rguenth at gcc dot gnu dot org 2009-11-13 20:03 ` rguenth at gcc dot gnu dot org [this message] 2009-11-13 20:52 ` paolo dot carlini at oracle dot com 2009-11-16 4:38 ` craig dot schlenter at gmail dot com 2010-05-04 12:06 ` paolo dot carlini at oracle dot com 2010-08-06 6:54 ` paolo dot carlini at oracle dot com [not found] <bug-42032-4@http.gcc.gnu.org/bugzilla/> 2011-09-25 16:04 ` paolo.carlini at oracle dot com 2011-09-25 16:08 ` evan at chromium dot org 2011-09-26 10:46 ` rguenth at gcc dot gnu.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=20091113200258.32351.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).