public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/111878] [14 Regression] ICE: in get_loop_exit_edges, at cfgloop.cc:1204 with -O3 -fgraphite-identity -fsave-optimization-record/-fdump-tree-graphite/-fopt-info Date: Mon, 30 Oct 2023 17:50:49 +0000 [thread overview] Message-ID: <bug-111878-4-Qe7e2Uvu8d@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111878-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111878 --- Comment #4 from Martin Jambor <jamborm at gcc dot gnu.org> --- I am not 100% certain if it is the same bug (I am happy to open a separate bug report if not), but I'm getting an ICE on the same spot, also with graphite, when running gfortran ~/gcc/trunk/src/libgomp/testsuite/libgomp.fortran/simd7.f90 -floop-nest-optimize -O1 with master revision 89e97f655d6 gfortran (and the above libgomp test).
next prev parent reply other threads:[~2023-10-30 17:50 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-19 11:57 [Bug tree-optimization/111878] New: [14 Regression] ICE: in get_loop_exit_edges, at cfgloop.cc:1204 with -O3 -fgraphite-identity -fsave-optimization-record zsojka at seznam dot cz 2023-10-19 12:07 ` [Bug tree-optimization/111878] " zsojka at seznam dot cz 2023-10-19 13:45 ` rguenth at gcc dot gnu.org 2023-10-19 18:45 ` pinskia at gcc dot gnu.org 2023-10-19 18:49 ` [Bug tree-optimization/111878] [14 Regression] ICE: in get_loop_exit_edges, at cfgloop.cc:1204 with -O3 -fgraphite-identity -fsave-optimization-record/-fdump-tree-graphite pinskia at gcc dot gnu.org 2023-10-30 17:50 ` jamborm at gcc dot gnu.org [this message] 2023-10-31 6:30 ` [Bug tree-optimization/111878] [14 Regression] ICE: in get_loop_exit_edges, at cfgloop.cc:1204 with -O3 -fgraphite-identity -fsave-optimization-record/-fdump-tree-graphite/-fopt-info sjames at gcc dot gnu.org 2023-10-31 8:57 ` [Bug tree-optimization/111878] [14 Regression] ICE: in get_loop_exit_edges, at cfgloop.cc:1204 with -O3 -fgraphite-identity -fsave-optimization-record/-fdump-tree-graphite/-fopt-info since r14-4708-gd65e38e616e7ac sjames at gcc dot gnu.org 2023-10-31 11:09 ` tnfchris at gcc dot gnu.org 2023-11-16 12:12 ` cvs-commit at gcc dot gnu.org 2023-11-16 12:14 ` tnfchris 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-111878-4-Qe7e2Uvu8d@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).