public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/63459] operator new and returns_nonnull Date: Sat, 04 Oct 2014 20:27:00 -0000 [thread overview] Message-ID: <bug-63459-4-v2O1ot5esS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63459-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63459 --- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> --- VRP already optimizes this, doesn't it? Adding an implicit __attribute__((nonnull(1))) to all C++ member functions might be good, but it also sounds a bit scary to me...
next prev parent reply other threads:[~2014-10-04 20:27 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-04 19:24 [Bug c++/63459] New: " hubicka at gcc dot gnu.org 2014-10-04 20:27 ` glisse at gcc dot gnu.org [this message] 2014-10-04 20:54 ` [Bug c++/63459] " hubicka at gcc dot gnu.org 2014-10-04 21:12 ` glisse at gcc dot gnu.org 2014-10-06 14:50 ` rguenth at gcc dot gnu.org 2014-10-08 17:59 ` hubicka at ucw dot cz 2014-10-08 18:19 ` hubicka at ucw dot cz 2014-11-29 19:34 ` glisse 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-63459-4-v2O1ot5esS@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).