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 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: Mon, 01 Aug 2022 11:51:45 +0000 [thread overview] Message-ID: <bug-106495-4-OtGZTO5WHQ@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 #3 from Richard Biener <rguenth at gcc dot gnu.org> --- OK, so it's indeed an isolated path we warn on: <bb 111> [local count: 2735590]: _46 = global_options.x_param_max_fsm_thread_path_insns; if (_46 <= n_insns_157) goto <bb 113>; [34.00%] else goto <bb 116>; [66.00%] <bb 116> [local count: 1805491]: n_insns_346 = ASSERT_EXPR <n_insns_157, n_insns_157 < _46>; _233 = m_path_340->m_vec; if (_233 != 0B) goto <bb 119>; [70.00%] else goto <bb 175>; [30.00%] <bb 175> [local count: 541647]: _379 = ASSERT_EXPR <_233, _233 == 0B>; <bb 117> [local count: 541647]: _286 = MEM[(struct vec *)0B].m_vecpfx.m_num; _381 = ASSERT_EXPR <0B, 0B != 0B>; if (_286 != 4294967295) goto <bb 120>; [0.00%] else goto <bb 118>; [100.00%] <bb 118> [local count: 541647]: _391 = ASSERT_EXPR <4294967294, 4294967294 < _286>; _290 = MEM <struct vec> [(struct basic_block_def * const &)_381].m_vecdata[4294967294]; goto <bb 122>; [100.00%]
next prev parent reply other threads:[~2022-08-01 11:51 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 [this message] 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 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-OtGZTO5WHQ@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).