public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107638] [13 Regression] options.h:239:36: error: token "." is not valid in preprocessor expressions Date: Tue, 15 Nov 2022 02:29:17 +0000 [thread overview] Message-ID: <bug-107638-4-GvnRUIjOCV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107638-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107638 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>: https://gcc.gnu.org/g:fce38b7d13ae625301571dcd84f3774ddaa6ed04 commit r13-4039-gfce38b7d13ae625301571dcd84f3774ddaa6ed04 Author: Patrick Palka <ppalka@redhat.com> Date: Mon Nov 14 21:28:58 2022 -0500 c++: init_priority and SUPPORTS_INIT_PRIORITY [PR107638] The commit r13-3706-gd0a492faa6478c for fixing the result of __has_attribute(init_priority) causes a bootstrap failure on hppa64-hpux due to assuming the macro SUPPORTS_INIT_PRIORITY expands to a simple constant, but on this target the macro is defined as #define SUPPORTS_INIT_PRIORITY (TARGET_GNU_LD ? 1 : 0) (where TARGET_GNU_LD expands to something in terms of global_options) which means we can't use the macro to conditionally exclude the entry for init_priority when defining the cxx_attribute_table. So instead of trying to exclude init_priority from the attribute table, this patch just makes __has_attribute handle init_priority specially. PR c++/107638 gcc/c-family/ChangeLog: * c-lex.cc (c_common_has_attribute): Return 1 for init_priority iff SUPPORTS_INIT_PRIORITY. gcc/cp/ChangeLog: * tree.cc (cxx_attribute_table): Don't conditionally exclude the init_priority entry. (handle_init_priority_attribute): Remove ATTRIBUTE_UNUSED. Return error_mark_node if !SUPPORTS_INIT_PRIORITY.
next prev parent reply other threads:[~2022-11-15 2:29 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-11 15:08 [Bug c++/107638] New: " danglin at gcc dot gnu.org 2022-11-11 16:25 ` [Bug c++/107638] " ppalka at gcc dot gnu.org 2022-11-13 9:04 ` jbglaw@lug-owl.de 2022-11-14 10:31 ` redi at gcc dot gnu.org 2022-11-14 11:26 ` rguenth at gcc dot gnu.org 2022-11-15 2:29 ` cvs-commit at gcc dot gnu.org [this message] 2022-11-15 14:44 ` jbglaw@lug-owl.de 2022-11-15 21:10 ` danglin 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-107638-4-GvnRUIjOCV@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).