public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [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 Date: Fri, 21 Apr 2023 07:57:50 +0000 [thread overview] Message-ID: <bug-109573-4-OwsBlt7TLx@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 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[12/13/14 regression] ICE |[11/12/13/14 regression] |in |ICE in |vectorizable_live_operation |vectorizable_live_operation |, at tree-vect-loop.cc:9060 |, at tree-vect-loop.cc:9060 |when building chromium's |when building chromium's |maglev-assembler-x64.cc |maglev-assembler-x64.cc |with -march=ivybridge |with -march=ivybridge since | |r11-3025-g095d42feed09f8 Keywords|needs-bisection | CC| |marxin at gcc dot gnu.org --- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> --- With -O3 (as with -O2 it started with the revision where we enabled vectorization at -O2), it started with r11-3025-g095d42feed09f8.
next prev parent reply other threads:[~2023-04-21 7:57 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-20 17:30 [Bug tree-optimization/109573] New: [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 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 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 ` marxin at gcc dot gnu.org [this message] 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 with -march=ivybridge since r11-3025-g095d42feed09f8 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-OwsBlt7TLx@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).