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 tree-optimization/103816] [12 Regression] ICE: in vect_build_slp_tree_2, at tree-vect-slp.c:1748 since r12-1551-g3dfa4fe9f1a089b2 Date: Wed, 05 Jan 2022 10:56:53 +0000 [thread overview] Message-ID: <bug-103816-4-yQxh8aLzjB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103816-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103816 --- Comment #4 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:1021b72bf6542f3c08e5404b65063216ee1b06f7 commit r12-6222-g1021b72bf6542f3c08e5404b65063216ee1b06f7 Author: Richard Biener <rguenther@suse.de> Date: Wed Jan 5 10:14:52 2022 +0100 tree-optimization/103816 - detect offset overflow in SLP group analysis This makes sure to detect overflow when computing DR_GROUP_GAP and DR_GROUP_SIZE more thoroughly so artificial testcases like the added one are not fooling the existing check. 2022-01-05 Richard Biener <rguenther@suse.de> PR tree-optimization/103816 * tree-vect-data-refs.c (vect_analyze_group_access_1): Also check DR_GROUP_GAP compute for overflow and representability. * gcc.dg/torture/pr103816.c: New testcase.
next prev parent reply other threads:[~2022-01-05 10:56 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-23 14:11 [Bug c/103816] New: ICE: in vect_build_slp_tree_2, at tree-vect-slp.c:1748 k.even-mendoza at imperial dot ac.uk 2021-12-23 14:54 ` [Bug tree-optimization/103816] [12 Regression] ICE: in vect_build_slp_tree_2, at tree-vect-slp.c:1748 since r12-1551-g3dfa4fe9f1a089b2 marxin at gcc dot gnu.org 2022-01-03 13:28 ` rguenth at gcc dot gnu.org 2022-01-05 9:07 ` rguenth at gcc dot gnu.org 2022-01-05 10:56 ` cvs-commit at gcc dot gnu.org [this message] 2022-01-05 11:04 ` 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-103816-4-yQxh8aLzjB@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).