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 fortran/97162] [11 Regression] ICE when building SPECCPU 2006 Gamess benchmark Date: Tue, 22 Sep 2020 14:07:25 +0000 [thread overview] Message-ID: <bug-97162-4-jFqzerEKa5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97162-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97162 --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- So just in case the following fixes it we've nailed it (somewhere I have a verifier written...) diff --git a/gcc/tree-predcom.c b/gcc/tree-predcom.c index b1d6e63559c..2f41ad222a0 100644 --- a/gcc/tree-predcom.c +++ b/gcc/tree-predcom.c @@ -3326,6 +3326,7 @@ tree_predictive_commoning (void) class loop *loop; unsigned ret = 0, changed = 0; + scev_reset (); initialize_original_copy_tables (); FOR_EACH_LOOP (loop, LI_ONLY_INNERMOST) if (optimize_loop_for_speed_p (loop))
next prev parent reply other threads:[~2020-09-22 14:07 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-22 11:34 [Bug fortran/97162] New: " tnfchris at gcc dot gnu.org 2020-09-22 12:05 ` [Bug fortran/97162] " marxin at gcc dot gnu.org 2020-09-22 12:19 ` marxin at gcc dot gnu.org 2020-09-22 12:58 ` tnfchris at gcc dot gnu.org 2020-09-22 14:05 ` rguenth at gcc dot gnu.org 2020-09-22 14:07 ` rguenth at gcc dot gnu.org [this message] 2020-09-22 14:11 ` marxin at gcc dot gnu.org 2020-09-23 7:09 ` rguenth at gcc dot gnu.org 2020-09-23 7:12 ` rguenth at gcc dot gnu.org 2020-09-23 8:09 ` cvs-commit at gcc dot gnu.org 2020-09-23 8:12 ` tnfchris at gcc dot gnu.org 2020-09-23 8:15 ` 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-97162-4-jFqzerEKa5@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).