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 rtl-optimization/114415] [13 Regression] wrong code with -Oz -fno-dce -fno-forward-propagate -flive-range-shrinkage -fweb since r13-1826 Date: Thu, 09 May 2024 10:04:15 +0000 [thread overview] Message-ID: <bug-114415-4-pTMZsUtL7s@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114415-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114415 --- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Vlad, do you plan to backport this to 13.3? One of the 2 release blockers we have for that release.
next prev parent reply other threads:[~2024-05-09 10:04 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-21 12:52 [Bug target/114415] New: wrong code with -Oz -fno-dce -fno-forward-propagate -flive-range-shrinkage -fweb zsojka at seznam dot cz 2024-03-25 14:43 ` [Bug target/114415] [13/14 Regression] wrong code with -Oz -fno-dce -fno-forward-propagate -flive-range-shrinkage -fweb since r13-1826 jakub at gcc dot gnu.org 2024-03-25 16:59 ` jakub at gcc dot gnu.org 2024-03-25 17:15 ` jakub at gcc dot gnu.org 2024-03-29 23:49 ` law at gcc dot gnu.org 2024-04-03 16:28 ` vmakarov at gcc dot gnu.org 2024-04-04 11:32 ` vmakarov at gcc dot gnu.org 2024-04-04 20:07 ` [Bug rtl-optimization/114415] " cvs-commit at gcc dot gnu.org 2024-04-05 4:10 ` [Bug rtl-optimization/114415] [13 " law at gcc dot gnu.org 2024-04-06 12:01 ` ebotcazou at gcc dot gnu.org 2024-04-06 17:35 ` law at gcc dot gnu.org 2024-05-08 12:28 ` rguenth at gcc dot gnu.org 2024-05-09 10:04 ` jakub at gcc dot gnu.org [this message] 2024-05-09 15:40 ` vmakarov at gcc dot gnu.org 2024-05-09 16:42 ` cvs-commit at gcc dot gnu.org 2024-05-09 19:06 ` 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-114415-4-pTMZsUtL7s@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).