public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56868] Constexpr example in 7.1.5/5 fails to compile correctly
Date: Sun, 07 Apr 2013 20:57:00 -0000 [thread overview]
Message-ID: <bug-56868-4-vDiFsKlQT6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56868-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56868
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> 2013-04-07 20:57:42 UTC ---
(In reply to comment #3)
> Whatever it is, doesn't have much to do with constexpr, consider:
That definitely makes it feel like 0*n being considered a null pointer constant
when it should not be.
next prev parent reply other threads:[~2013-04-07 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 18:36 [Bug c++/56868] New: " g++bug at oxyware dot com
2013-04-07 18:39 ` [Bug c++/56868] " g++bug at oxyware dot com
2013-04-07 18:42 ` redi at gcc dot gnu.org
2013-04-07 18:51 ` pinskia at gcc dot gnu.org
2013-04-07 19:41 ` paolo.carlini at oracle dot com
2013-04-07 20:57 ` pinskia at gcc dot gnu.org [this message]
2013-04-07 21:10 ` paolo.carlini at oracle dot com
2013-04-07 21:32 ` daniel.kruegler at googlemail dot com
2015-04-27 17:48 ` ktietz 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-56868-4-vDiFsKlQT6@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: link
Be 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).