public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/49171] New: [C++0x][constexpr] Constant expressions support reinterpret_cast Date: Thu, 26 May 2011 12:10:00 -0000 [thread overview] Message-ID: <bug-49171-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49171 Summary: [C++0x][constexpr] Constant expressions support reinterpret_cast Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: daniel.kruegler@googlemail.com CC: jason@redhat.com gcc 4.7.0 20110521 (experimental) in C++0x mode accepts the following code: //--- constexpr const char* c = reinterpret_cast<const char*>(0x123); //--- As of FDIS 5.19 p2 b13 reinterpret_cast is no longer supported in constant expressions, therefore the code should be rejected. I'm emphasizing this because gcc should at least try to implement this to find out, how much code will break because of this change.
next reply other threads:[~2011-05-26 12:05 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-26 12:10 daniel.kruegler at googlemail dot com [this message] 2011-05-26 12:13 ` [Bug c++/49171] " daniel.kruegler at googlemail dot com 2011-08-30 9:52 ` daniel.kruegler at googlemail dot com 2012-10-03 14:28 ` paolo.carlini at oracle dot com 2012-10-03 16:22 ` daniel.kruegler at googlemail dot com 2012-10-03 16:46 ` paolo.carlini at oracle dot com 2012-10-03 18:46 ` daniel.kruegler at googlemail dot com 2012-10-05 14:10 ` paolo.carlini at oracle dot com 2012-10-05 14:17 ` daniel.kruegler at googlemail dot com 2012-10-23 23:00 ` paolo.carlini at oracle dot com 2012-10-23 23:02 ` paolo.carlini at oracle dot com 2014-11-18 13:44 ` jason at gcc dot gnu.org 2015-04-27 17:51 ` ktietz at gcc dot gnu.org 2015-08-23 16:41 ` myriachan at gmail dot com
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-49171-4@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).