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 tree-optimization/104162] [12 Regression] Missed CSE after lowering of &MEM[ptr_1 + CST] Date: Tue, 21 May 2024 09:11:05 +0000 [thread overview] Message-ID: <bug-104162-4-u6sVqRE4Ja@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104162-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104162 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|13.3 |13.4 --- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
prev parent reply other threads:[~2024-05-21 9:11 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-21 13:01 [Bug tree-optimization/104162] New: " rguenth at gcc dot gnu.org 2022-01-21 13:01 ` [Bug tree-optimization/104162] " rguenth at gcc dot gnu.org 2022-01-21 13:13 ` rguenth at gcc dot gnu.org 2022-01-21 16:10 ` pinskia at gcc dot gnu.org 2022-01-24 9:50 ` rguenth at gcc dot gnu.org 2022-01-26 13:48 ` rguenth at gcc dot gnu.org 2022-01-26 14:39 ` rguenth at gcc dot gnu.org 2022-03-23 12:32 ` rguenth at gcc dot gnu.org 2022-05-05 12:41 ` [Bug tree-optimization/104162] [12/13 " cvs-commit at gcc dot gnu.org 2022-12-12 13:32 ` [Bug tree-optimization/104162] [12 " marxin at gcc dot gnu.org 2023-04-26 6:55 ` rguenth at gcc dot gnu.org 2023-07-27 9:22 ` rguenth at gcc dot gnu.org 2024-05-21 9:11 ` jakub at gcc dot gnu.org [this message]
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-104162-4-u6sVqRE4Ja@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).