public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "r_new at rambler dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/94753] New: -undef, c++20 and feature-test macros
Date: Fri, 24 Apr 2020 23:22:31 +0000	[thread overview]
Message-ID: <bug-94753-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94753

            Bug ID: 94753
           Summary: -undef, c++20 and feature-test macros
           Product: gcc
           Version: 10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: preprocessor
          Assignee: unassigned at gcc dot gnu.org
          Reporter: r_new at rambler dot ru
  Target Milestone: ---

In c++20 feature-test macros (_­_­cpp_­attributes, _­_­cpp_­constexpr, ...) are
standard predefined macros, must be predefined even with -undef.

g++ -undef -std=c++2a -E -dM -x c++ - < /dev/null 
#define __STDC_HOSTED__ 1
#define __STDC_IEC_559__ 1
#define __STDC_ISO_10646__ 201706L
#define __STDC_UTF_16__ 1
#define __cplusplus 201709L
#define _STDC_PREDEF_H 1
#define __STDC_IEC_559_COMPLEX__ 1
#define __STDC_UTF_32__ 1
#define __STDC__ 1
#define _GNU_SOURCE 1

gcc version 10.0.1 20200423 (experimental) (Compiler-Explorer-Build) and gcc
version 9.3.0 (Arch Linux 9.3.0-1)

             reply	other threads:[~2020-04-24 23:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 23:22 r_new at rambler dot ru [this message]
2020-04-25 13:47 ` [Bug preprocessor/94753] " redi at gcc dot gnu.org
2024-04-13 23:29 ` [Bug c++/94753] " pinskia at gcc dot gnu.org
2024-04-24 22:54 ` pinskia at gcc dot gnu.org
2024-04-25 11:58 ` r_new at rambler dot ru
2024-04-25 16:19 ` redi at gcc dot gnu.org
2024-04-25 16:26 ` 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-94753-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: 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).