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/106912] [13 Regression] ICE in vect_transform_loops, at tree-vectorizer.cc:1032 since r13-1575-gcf3a120084e94614 Date: Tue, 13 Sep 2022 06:41:40 +0000 [thread overview] Message-ID: <bug-106912-4-osiKcH5PNr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106912-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106912 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org Status|NEW |ASSIGNED Priority|P3 |P1 Target Milestone|--- |13.0 Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed, we have # .MEM = VDEF <.MEM> vect__5.57_58 = foo.simdclone.0 (vect__4.56_57); here. IIRC I filed a bugreport about simdclones not being const when the scalar version is, in this case it's possibly IPA pure const not updating the clones before materializing them!? That said, the not vectorized variant is just _5 = foo (_4); and without -fprofile-generate the vectorized variant also keeps 'const'. I will look at this again after Cauldron. Have to dig to where the simdclone is actually generated.
next prev parent reply other threads:[~2022-09-13 6:41 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-12 17:23 [Bug c/106912] New: [13 Regression] ICE in vect_transform_loops, at tree-vectorizer.cc:1032 gscfq@t-online.de 2022-09-12 19:35 ` [Bug tree-optimization/106912] [13 Regression] ICE in vect_transform_loops, at tree-vectorizer.cc:1032 since r13-1575-gcf3a120084e94614 marxin at gcc dot gnu.org 2022-09-13 6:41 ` rguenth at gcc dot gnu.org [this message] 2022-09-13 7:47 ` rguenth at gcc dot gnu.org 2022-09-13 8:51 ` rguenth at gcc dot gnu.org 2022-11-25 7:59 ` rguenth at gcc dot gnu.org 2022-12-08 17:30 ` jakub at gcc dot gnu.org 2022-12-12 10:56 ` rguenth at gcc dot gnu.org 2022-12-20 0:12 ` pinskia at gcc dot gnu.org 2023-02-06 12:11 ` jakub at gcc dot gnu.org 2023-02-06 12:29 ` jakub at gcc dot gnu.org 2023-02-07 11:33 ` rguenth at gcc dot gnu.org 2023-03-16 12:50 ` jakub at gcc dot gnu.org 2023-03-24 12:53 ` cvs-commit at gcc dot gnu.org 2023-03-24 12:54 ` 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-106912-4-osiKcH5PNr@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).