public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109744] mesa/panvk: bogus Warray-bounds on gcc 12.2, fixed in 13 branch Date: Wed, 10 Jan 2024 17:47:18 +0000 [thread overview] Message-ID: <bug-109744-4-JJK4RwvqXD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109744-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109744 Martin Jambor <jamborm at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|needs-bisection | --- Comment #3 from Martin Jambor <jamborm at gcc dot gnu.org> --- The warning went away with commit r13-4389-gfd8dd6c0384969 (Richard Biener: tree-optimization/107852 - missed optimization with PHIs).
next prev parent reply other threads:[~2024-01-10 17:47 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-05 9:16 [Bug c/109744] New: " david at ixit dot cz 2023-05-05 9:33 ` [Bug c/109744] mesa/panvk: " sjames at gcc dot gnu.org 2023-05-05 20:08 ` [Bug tree-optimization/109744] " david at ixit dot cz 2024-01-10 17:47 ` jamborm at gcc dot gnu.org [this message] 2024-01-20 19:49 ` 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-109744-4-JJK4RwvqXD@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).