public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115661] [15 Regression] wrong code at -O{2,3} on x86_64-linux-gnu since r15-1599-g63512c72df09b4 Date: Thu, 27 Jun 2024 05:00:43 +0000 [thread overview] Message-ID: <bug-115661-4-d7XOvFoZOX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115661-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115661 --- Comment #7 from Sam James <sjames at gcc dot gnu.org> --- To the reporter: I should say, thanks for finding this so quickly - it made it a lot easier to debug.
next prev parent reply other threads:[~2024-06-27 5:00 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-26 10:06 [Bug tree-optimization/115661] New: wrong code at -O{2,3} on x86_64-linux-gnu zhendong.su at inf dot ethz.ch 2024-06-26 10:14 ` [Bug tree-optimization/115661] " zhendong.su at inf dot ethz.ch 2024-06-26 10:35 ` [Bug tree-optimization/115661] [15 Regression] " rguenth at gcc dot gnu.org 2024-06-26 11:29 ` sjames at gcc dot gnu.org 2024-06-26 11:34 ` [Bug tree-optimization/115661] [15 Regression] wrong code at -O{2,3} on x86_64-linux-gnu since r15-1599-g63512c72df09b4 sjames at gcc dot gnu.org 2024-06-26 12:27 ` sjames at gcc dot gnu.org 2024-06-26 13:30 ` [Bug target/115661] " rguenth at gcc dot gnu.org 2024-06-26 18:43 ` Evgeny.Karpov at microsoft dot com 2024-06-26 23:45 ` sjames at gcc dot gnu.org 2024-06-27 5:00 ` sjames at gcc dot gnu.org [this message] 2024-06-27 7:24 ` Evgeny.Karpov at microsoft dot com 2024-06-28 12:47 ` cvs-commit at gcc dot gnu.org 2024-06-28 12:50 ` clyon 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-115661-4-d7XOvFoZOX@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).