public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/106495] [13 Regression] Build fails gcc/tree-ssa-threadbackward.cc:22: gcc/vec.h:890:19: error: array subscript 4294967294 is above array bounds of 'basic_block_def* [1]' [-Werror=array-bounds] Date: Tue, 02 Aug 2022 06:35:31 +0000 [thread overview] Message-ID: <bug-106495-4-Mg7X5G8pMG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106495-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106495 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:b9da686470d1c23929eefb401280ad8ba17e2a58 commit r13-1924-gb9da686470d1c23929eefb401280ad8ba17e2a58 Author: Richard Biener <rguenther@suse.de> Date: Mon Aug 1 14:59:08 2022 +0200 tree-optimization/106495 - avoid threading to possibly never executed edge The following builds upon the logic of the PR105679 fix by avoiding to thread to a known edge that is predicted as probably never executed. PR tree-optimization/106495 * tree-ssa-threadbackward.cc (back_threader_profitability::profitable_path_p): If known_edge is probably never executed avoid threading.
next prev parent reply other threads:[~2022-08-02 6:35 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-01 6:29 [Bug middle-end/106495] New: " slyfox at gcc dot gnu.org 2022-08-01 8:38 ` [Bug middle-end/106495] " pinskia at gcc dot gnu.org 2022-08-01 9:22 ` rguenth at gcc dot gnu.org 2022-08-01 11:51 ` rguenth at gcc dot gnu.org 2022-08-01 12:17 ` rguenth at gcc dot gnu.org 2022-08-01 12:21 ` rguenth at gcc dot gnu.org 2022-08-01 12:33 ` rguenth at gcc dot gnu.org 2022-08-01 12:58 ` rguenth at gcc dot gnu.org 2022-08-01 13:04 ` rguenth at gcc dot gnu.org 2022-08-01 13:58 ` aldyh at gcc dot gnu.org 2022-08-02 6:35 ` cvs-commit at gcc dot gnu.org [this message] 2022-08-02 6:35 ` rguenth 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-106495-4-Mg7X5G8pMG@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).