public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60304] Including <atomic> disables -Wconversion-null
Date: Fri, 24 Oct 2014 09:35:00 -0000 [thread overview]
Message-ID: <bug-60304-4-87NLE1Vv8g@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60304-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60304
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Paolo Carlini from comment #5)
> #define false false
No idea what's going on, but I think I have a patch somewhere to disable that
macro for C++, it's very explicitly non-conforming:
[support.runtime]/8
"The header <cstdbool> and the header <stdbool.h> shall not define macros named
bool, true, or false."
Let me dig out the old patch. I also remember some discussion with Joseph IIRC.
next prev parent reply other threads:[~2014-10-24 9:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 15:59 [Bug preprocessor/60304] New: " bug-reports at psdtechnologies dot com
2014-02-21 18:24 ` [Bug preprocessor/60304] " harald at gigawatt dot nl
2014-10-24 9:05 ` [Bug c++/60304] " paolo.carlini at oracle dot com
2014-10-24 9:29 ` paolo.carlini at oracle dot com
2014-10-24 9:35 ` redi at gcc dot gnu.org [this message]
2014-10-24 9:44 ` paolo.carlini at oracle dot com
2014-10-24 9:51 ` redi at gcc dot gnu.org
2014-10-24 11:33 ` paolo.carlini at oracle dot com
2014-10-24 12:01 ` redi at gcc dot gnu.org
2014-10-24 12:27 ` jakub at gcc dot gnu.org
2014-10-24 13:19 ` redi at gcc dot gnu.org
2014-10-24 13:23 ` manu at gcc dot gnu.org
2014-10-24 13:49 ` manu at gcc dot gnu.org
2014-10-24 14:51 ` redi at gcc dot gnu.org
2014-10-24 16:20 ` manu at gcc dot gnu.org
2020-09-02 15:32 ` [Bug c++/60304] Including <stdbool.h> disables -Wconversion-null in C++ 98 mode redi at gcc dot gnu.org
2020-09-02 15:58 ` redi at gcc dot gnu.org
2020-09-02 16:03 ` redi at gcc dot gnu.org
2020-09-02 19:50 ` cvs-commit at gcc dot gnu.org
2020-09-02 19:52 ` redi at gcc dot gnu.org
2020-09-05 11:13 ` harald at gigawatt dot nl
2020-09-05 12:12 ` redi 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-60304-4-87NLE1Vv8g@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).