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/109573] [12/13/14 regression] ICE in vectorizable_live_operation, at tree-vect-loop.cc:9060 when building chromium's maglev-assembler-x64.cc with -march=ivybridge Date: Fri, 21 Apr 2023 07:07:10 +0000 [thread overview] Message-ID: <bug-109573-4-LYkRTBhurU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109573-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109573 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Priority|P3 |P2 Last reconfirmed| |2023-04-21 Status|UNCONFIRMED |ASSIGNED Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- The assert is just a bit overzealous. (gdb) p debug_bb ($2) <bb 47> [local count: 708959595]: # prephitmp_152 = PHI <_276(45), pretmp_2(46)> # prephitmp_205 = PHI <_85(45), pretmp_341(46)> # prephitmp_556 = PHI <_86(45), pretmp_298(46)> # prephitmp_353 = PHI <_275(45), pretmp_555(46)> result_282 = (void *) prephitmp_152; _283 = prephitmp_152 + 8; MEM[(struct Zone *)_86].position_ = _283; vectp.1975_450 = result_282; MEM <vector(2) int> [(int *)vectp.1975_450] = { 0, 0 }; use_stmt is the last stmt so code is SSA_NAME. But it's also an odd SLP graph as we have two graphs we vectorize separately where parts of one graph are used in address computes of another (the addresses we don't model in SLP so we "fail" to merge the SLP graphs). Going to be interesting to see whether a reduced testcase reproduces that. Anyway, the easiest "fix" is to simply remove the assert. The assert is not technically necessary, it's just there trying to "prove" we understand the situations this hack is necessary (I don't think we do ;)).
next prev parent reply other threads:[~2023-04-21 7:07 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-20 17:30 [Bug tree-optimization/109573] New: " sjames at gcc dot gnu.org 2023-04-20 19:18 ` [Bug tree-optimization/109573] " pinskia at gcc dot gnu.org 2023-04-20 21:13 ` pinskia at gcc dot gnu.org 2023-04-21 7:07 ` rguenth at gcc dot gnu.org [this message] 2023-04-21 7:35 ` sjames at gcc dot gnu.org 2023-04-21 7:53 ` rguenth at gcc dot gnu.org 2023-04-21 7:57 ` [Bug tree-optimization/109573] [11/12/13/14 regression] ICE in vectorizable_live_operation, at tree-vect-loop.cc:9060 when building chromium's maglev-assembler-x64.cc with -march=ivybridge since r11-3025-g095d42feed09f8 marxin at gcc dot gnu.org 2023-04-21 8:07 ` [Bug tree-optimization/109573] [11/12/13/14 regression] ICE in vectorizable_live_operation, at tree-vect-loop.cc:9060 " marxin at gcc dot gnu.org 2023-04-21 11:47 ` cvs-commit at gcc dot gnu.org 2023-04-26 9:33 ` [Bug tree-optimization/109573] [11/12/13 " cvs-commit at gcc dot gnu.org 2023-04-26 10:41 ` cvs-commit at gcc dot gnu.org 2023-05-02 12:40 ` [Bug tree-optimization/109573] [11 " cvs-commit at gcc dot gnu.org 2023-05-02 12:40 ` rguenth at gcc dot gnu.org 2023-05-03 8:46 ` jakub at gcc dot gnu.org 2023-05-03 9:28 ` rguenth at gcc dot gnu.org 2023-05-08 6:20 ` rguenth at gcc dot gnu.org 2023-05-29 10:08 ` jakub 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-109573-4-LYkRTBhurU@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).