public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug build/26187] [-std=gnu++17] gdb/inferior.h: error: ‘bool std::uncaught_exception()’ is deprecated [-Werror=deprecated-declarations] Date: Sun, 05 Jul 2020 10:02:50 +0000 [thread overview] Message-ID: <bug-26187-4717-4StJ96StIw@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26187-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26187 --- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> --- (In reply to Tom Tromey from comment #4) > Should this check the macro value against 201411? > See https://en.cppreference.com/w/User:D41D8CD98F/feature_testing_macros Ah, I didn't realize that the macro had a meaningful value. But at https://isocpp.org/std/standing-documents/sd-6-sg10-feature-test-recommendations , I read: ... The value specified for a feature-test macro is based on the year and month in which the feature is voted into the working draft. In a case where a feature is subsequently changed in a significant way, but arguably remains the same feature, the value of the macro is changed to indicate the “revision level” of the specification of the feature. However, in most cases it is expected that the presence of a feature can be determined by the presence of any non-zero macro value ... They use: ... #if __cpp_lib_is_final ... instead of #ifdef though in the example, so I suppose I'll do the same. > Otherwise it seems fine to me. Ack, I'll commit then. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-07-05 10:02 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-30 11:27 [Bug ada/26187] New: Can't build gdb with current GCC master vries at gcc dot gnu.org 2020-06-30 12:14 ` [Bug build/26187] [-std=gnu++17] gdb/inferior.h: error: ‘bool std::uncaught_exception()’ is deprecated [-Werror=deprecated-declarations] vries at gcc dot gnu.org 2020-07-04 17:23 ` tromey at sourceware dot org 2020-07-05 10:02 ` vries at gcc dot gnu.org [this message] 2020-07-05 21:47 ` cvs-commit at gcc dot gnu.org 2020-07-05 21:48 ` vries 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-26187-4717-4StJ96StIw@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).