public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/104669] [11/12 Regression] ICE in is_function_default_version, at attribs.cc:1219 Date: Wed, 23 Feb 2022 22:03:48 +0000 [thread overview] Message-ID: <bug-104669-4-jKNwIZ9wCb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104669-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104669 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-invalid-code, | |ice-on-valid-code --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note here is the valid C++ code: void bar() { int foo(void); int foo(void) __attribute__((target("sse"))); int foo(void) __attribute__((target("default"))); int (*p)(void) = &foo; return; }
next prev parent reply other threads:[~2022-02-23 22:03 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-23 18:00 [Bug c++/104669] New: " gscfq@t-online.de 2022-02-23 19:44 ` [Bug c++/104669] " mpolacek at gcc dot gnu.org 2022-02-23 22:03 ` pinskia at gcc dot gnu.org [this message] 2022-03-03 11:47 ` jakub at gcc dot gnu.org 2022-03-09 12:59 ` rguenth at gcc dot gnu.org 2022-04-12 14:35 ` jason at gcc dot gnu.org 2022-04-12 21:09 ` cvs-commit at gcc dot gnu.org 2022-04-21 7:51 ` [Bug c++/104669] [11 " rguenth at gcc dot gnu.org 2022-05-12 20:13 ` cvs-commit at gcc dot gnu.org 2022-05-12 20:22 ` jason at gcc dot gnu.org 2024-03-11 5:17 ` 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-104669-4-jKNwIZ9wCb@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).