public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/104165] [12 Regression] -Warray-bounds for unreachable code inlined from std::sort() Date: Tue, 06 Dec 2022 07:29:25 +0000 [thread overview] Message-ID: <bug-104165-4-amWOxKgYEo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104165-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104165 --- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> --- I have opened PR107986 for the testcase in comment#2 which isn't yet fixed on trunk.
next prev parent reply other threads:[~2022-12-06 7:29 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-21 15:40 [Bug c++/104165] New: Incorrectly identifying array bounds with -O2 -Werror=array-bounds kbrabml at gmail dot com 2022-01-21 17:04 ` [Bug tree-optimization/104165] [12 Regression] " pinskia at gcc dot gnu.org 2022-01-21 17:16 ` [Bug tree-optimization/104165] [12 Regression] -Warray-bounds for unreachable code inlined from std::sort() msebor at gcc dot gnu.org 2022-02-08 21:07 ` msebor at gcc dot gnu.org 2022-05-06 8:32 ` [Bug tree-optimization/104165] [12/13 " jakub at gcc dot gnu.org 2022-07-26 13:03 ` rguenth at gcc dot gnu.org 2022-12-05 15:39 ` [Bug tree-optimization/104165] [12 " rguenth at gcc dot gnu.org 2022-12-05 16:05 ` jakub at gcc dot gnu.org 2022-12-06 7:24 ` cvs-commit at gcc dot gnu.org 2022-12-06 7:29 ` rguenth at gcc dot gnu.org [this message] 2023-05-08 12:23 ` rguenth at gcc dot gnu.org 2023-09-27 12:36 ` fchelnokov at gmail dot com
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-104165-4-amWOxKgYEo@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).