public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "froydnj at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/52231] [missed optimization/diagnostics] address-of-reference Date: Wed, 18 Feb 2015 19:44:00 -0000 [thread overview] Message-ID: <bug-52231-4-H2a3HIHZDT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52231-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52231 --- Comment #5 from Nathan Froyd <froydnj at gcc dot gnu.org> --- FWIW, clang (>= 3.5) understands how to optimize the original testcase in comment 0; it even issues a -Wtautological-undefined-compare warning. This also showed up in the context of trying to hint to the compiler that placement new didn't need null checks: #include <new> void init(int& p) { new (&p) float(3.14f); } which clang understands how to optimize and GCC does not.
next prev parent reply other threads:[~2015-02-18 19:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-13 13:33 [Bug c++/52231] New: " pluto at agmk dot net 2012-02-13 17:56 ` [Bug c++/52231] " pinskia at gcc dot gnu.org 2012-02-13 18:13 ` redi at gcc dot gnu.org 2012-02-13 18:19 ` redi at gcc dot gnu.org 2015-02-18 19:36 ` pinskia at gcc dot gnu.org 2015-02-18 19:44 ` froydnj at gcc dot gnu.org [this message] 2015-02-18 21:30 ` redi at gcc dot gnu.org 2015-02-18 22:04 ` froydnj 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-52231-4-H2a3HIHZDT@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).