public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/112339] ICE with clang::no_sanitize and -fsanitize= Date: Thu, 02 Nov 2023 09:45:41 +0000 [thread overview] Message-ID: <bug-112339-4-0vSqtsAnQq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112339-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112339 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 56488 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56488&action=edit gcc14-pr112339.patch Indeed. For -Wno-attributes= registered attributes we don't really parse their arguments and there is no handler for them, so if they are added, their argument will be always error_mark_node and they'll just confuse any lookup_attribute done later. I must say I'm a little bit afraid of what happens when one uses -Wno-attributes=gnu:: or -Wno-attributes=gnu::some_standard_gnu_attribute, but this patch shouldn't make that worse.
next prev parent reply other threads:[~2023-11-02 9:45 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-01 18:37 [Bug c++/112339] New: ICE with namespaced attribute on function s_gccbugzilla at nedprod dot com 2023-11-01 18:45 ` [Bug sanitizer/112339] ICE with clang::no_sanitize and -fsanitize= pinskia at gcc dot gnu.org 2023-11-02 9:45 ` jakub at gcc dot gnu.org [this message] 2023-11-08 22:32 ` [Bug c/112339] " s_gccbugzilla at nedprod dot com 2023-11-09 8:07 ` cvs-commit at gcc dot gnu.org 2023-12-05 16:32 ` cvs-commit at gcc dot gnu.org 2023-12-16 0:37 ` cvs-commit at gcc dot gnu.org 2023-12-16 8:46 ` jakub 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-112339-4-0vSqtsAnQq@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).