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 tree-optimization/115395] [15 regression] libarchive miscompiled with -O2 -march=znver2 -fno-vect-cost-model since r15-1006-gd93353e6423eca Date: Mon, 10 Jun 2024 11:20:29 +0000 [thread overview] Message-ID: <bug-115395-4-ZtBe3rS0Nn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115395-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115395 --- Comment #9 from Sam James <sjames at gcc dot gnu.org> --- Thanks for the quick fix! We had another issue which bisected to the same, but it was far harder to reduce so we decided to wait. Hopefully fixed by this too.
prev parent reply other threads:[~2024-06-10 11:20 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-08 12:24 [Bug tree-optimization/115395] New: [15 regression] libarchive miscompiled with -O2 -march=znver2 -fno-vect-cost-model sjames at gcc dot gnu.org 2024-06-08 12:30 ` [Bug tree-optimization/115395] " pinskia at gcc dot gnu.org 2024-06-08 12:37 ` pinskia at gcc dot gnu.org 2024-06-08 13:45 ` [Bug tree-optimization/115395] [15 regression] libarchive miscompiled with -O2 -march=znver2 -fno-vect-cost-model since r15-1006-gd93353e6423eca sjames at gcc dot gnu.org 2024-06-08 16:11 ` sjames at gcc dot gnu.org 2024-06-10 6:39 ` rguenth at gcc dot gnu.org 2024-06-10 7:31 ` rguenth at gcc dot gnu.org 2024-06-10 8:03 ` rguenth at gcc dot gnu.org 2024-06-10 9:39 ` cvs-commit at gcc dot gnu.org 2024-06-10 9:49 ` rguenth at gcc dot gnu.org 2024-06-10 11:20 ` sjames 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-115395-4-ZtBe3rS0Nn@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).