public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lutztonineubert at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/106921] [11/12/13/14 Regression] -O1 and -fipa-icf -fpartial-inlining causes wrong code since r11-4987-g602c6cfc79ce4ae6 Date: Tue, 21 Nov 2023 08:41:01 +0000 [thread overview] Message-ID: <bug-106921-4-nRlfuV58Tu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106921-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106921 --- Comment #8 from Toni Neubert <lutztonineubert at gmail dot com> --- Hello, I just wanted to ask what the state of this bug is? I think that incorrectly compiled code should be much more important than anything else since any system can be affected without even knowing it. I know that a lot of things happen here on a voluntary basis and I value that very much. What can we do to give such bugs a hire priority or help to solve such things?
next prev parent reply other threads:[~2023-11-21 8:41 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-13 6:55 [Bug c++/106921] New: [11/12.1] -O1 and -fipa-icf -fpartial-inlining causes wrong code lutztonineubert at gmail dot com 2022-09-13 9:17 ` [Bug c++/106921] " rguenth at gcc dot gnu.org 2022-09-13 11:31 ` [Bug c++/106921] [11/12/13 Regression] -O1 and -fipa-icf -fpartial-inlining causes wrong code since r11-4987-g602c6cfc79ce4ae6 marxin at gcc dot gnu.org 2022-09-25 7:01 ` lutztonineubert at gmail dot com 2022-09-26 9:33 ` marxin at gcc dot gnu.org 2022-10-18 7:52 ` rguenth at gcc dot gnu.org 2022-12-28 14:43 ` marxin at gcc dot gnu.org 2023-02-23 10:15 ` [Bug ipa/106921] " tkapela at poczta dot fm 2023-05-29 10:07 ` [Bug ipa/106921] [11/12/13/14 " jakub at gcc dot gnu.org 2023-11-21 8:41 ` lutztonineubert at gmail dot com [this message] 2024-03-09 21:11 ` 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-106921-4-nRlfuV58Tu@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).