public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/106816] noreturn/pure attributes are not set correctly on multiversioned functions Date: Wed, 14 Sep 2022 13:59:08 +0000 [thread overview] Message-ID: <bug-106816-4-hVjEbxOalo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106816-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106816 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot gnu.org Status|NEW |ASSIGNED --- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> --- Let me assign it to myself.
next prev parent reply other threads:[~2022-09-14 13:59 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-02 15:34 [Bug ipa/106816] New: " gcc.gnu at vvalter dot com 2022-09-02 17:26 ` [Bug ipa/106816] " hjl.tools at gmail dot com 2022-09-02 17:55 ` gcc.gnu at vvalter dot com 2022-09-02 18:39 ` hjl.tools at gmail dot com 2022-09-02 19:48 ` gcc.gnu at vvalter dot com 2022-09-05 10:02 ` rguenth at gcc dot gnu.org 2022-09-14 13:58 ` marxin at gcc dot gnu.org 2022-09-14 13:59 ` marxin at gcc dot gnu.org [this message] 2022-12-28 14:50 ` marxin at gcc dot gnu.org 2023-01-03 10:27 ` jamborm at gcc dot gnu.org 2023-01-06 15:17 ` marxin at gcc dot gnu.org 2023-04-03 9:03 ` marxin at gcc dot gnu.org 2023-04-26 6:56 ` rguenth at gcc dot gnu.org 2023-07-27 9:23 ` rguenth at gcc dot gnu.org 2024-05-21 9:12 ` 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-106816-4-hVjEbxOalo@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).