public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51270] constness violation is accepted without any warning but leads to a required function call being eliminated during optimization Date: Tue, 22 Nov 2011 16:11:00 -0000 [thread overview] Message-ID: <bug-51270-4-bmL09XCjoE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51270-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51270 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |diagnostic --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-11-22 15:55:41 UTC --- This variation is a bit closer to your original and doesn't get a warning: int*& faulty_compiled_function(char*& val) { char const* const& tmp = (const char*)val; return (int*&)tmp; } So maybe there is a missed warning bug. Other compilers miss it too.
next prev parent reply other threads:[~2011-11-22 15:56 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-22 15:41 [Bug c++/51270] New: " michiel_dewilde at agilent dot com 2011-11-22 15:45 ` [Bug c++/51270] " michiel_dewilde at agilent dot com 2011-11-22 15:50 ` redi at gcc dot gnu.org 2011-11-22 16:10 ` redi at gcc dot gnu.org 2011-11-22 16:11 ` redi at gcc dot gnu.org [this message] 2011-11-22 16:55 ` [Bug c++/51270] missed warning about returning reference to temporary redi at gcc dot gnu.org 2011-11-22 18:50 ` michiel_dewilde at agilent dot com 2011-11-22 19:23 ` redi at gcc dot gnu.org 2011-11-22 20:49 ` redi 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=bug-51270-4-bmL09XCjoE@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).