public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jyasskin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/52145] [C++11] [DR 903] zero-valued integer constant expression should prefer conversion to pointer Date: Thu, 26 Apr 2012 19:43:00 -0000 [thread overview] Message-ID: <bug-52145-4-NGNPicqQHu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52145-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52145 Jeffrey Yasskin <jyasskin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|SUSPENDED |NEW CC| |jyasskin at gcc dot gnu.org --- Comment #3 from Jeffrey Yasskin <jyasskin at gcc dot gnu.org> 2012-04-26 19:42:19 UTC --- A simpler test case is: $ cat test.cc const long kNullPtr = 0; const long* ptr = kNullPtr; $ g++-4.7pre -c test.cc -std=gnu++11 test.cc:2:19: error: invalid conversion from ‘long int’ to ‘const long int*’ [-fpermissive] $ g++-4.7pre --version g++-4.7pre (GCC) 4.7.1 20120412 (prerelease) I'm going to unsuspend this because DR903 is "ready", and gcc-4.7's behavior doesn't match either the proposed wording or the current definition of C++11. The proposed wording discusses a change to C++17 rather than to C++11 (we can tell because it adds a "C.3 C++ and ISO C++ 2011" section), so the new error should only show up under -std=gnu++17, and be a warning in -std=gnu++11.
next prev parent reply other threads:[~2012-04-26 19:43 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-07 1:00 [Bug c++/52145] New: [C++11] " zeratul976 at hotmail dot com 2012-02-07 13:52 ` [Bug c++/52145] " daniel.kruegler at googlemail dot com 2012-02-07 14:39 ` [Bug c++/52145] [C++11] [DR 903] " redi at gcc dot gnu.org 2012-04-26 19:43 ` jyasskin at gcc dot gnu.org [this message] 2012-04-26 23:03 ` paolo.carlini at oracle dot com 2012-04-26 23:06 ` jyasskin at gcc dot gnu.org 2012-04-26 23:14 ` paolo.carlini at oracle dot com 2012-04-26 23:57 ` jyasskin at gcc dot gnu.org 2014-12-10 13:30 ` redi at gcc dot gnu.org 2021-12-04 6:43 ` pinskia at gcc dot gnu.org 2021-12-04 6:43 ` pinskia at gcc dot gnu.org 2021-12-04 6:52 ` pinskia at gcc dot gnu.org 2021-12-07 12:39 ` pinskia at gcc dot gnu.org 2022-10-14 15:14 ` pinskia 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-52145-4-NGNPicqQHu@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).