public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/95323] ice in compute_live_loop_exits, at tree-ssa-loop-manip.c:247
Date: Mon, 25 May 2020 21:28:26 +0000 [thread overview]
Message-ID: <bug-95323-4-ndzv4ht5mU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95323-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95323
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |anlauf at gcc dot gnu.org
Component|fortran |tree-optimization
Status|WAITING |NEW
--- Comment #4 from anlauf at gcc dot gnu.org ---
(In reply to David Binderman from comment #3)
> (In reply to anlauf from comment #1)
> > local.f90:3: Error: Can't open included file 'SIZES'
> >
> > Please include everything needed to reproduce.
>
> Done.
>
> > Are you sure this is a fortran bug, rather than tree-optimization?
>
> Not using -O2 makes the code compile, so something in the optimiser
> is going wrong, triggered by Fortran source code.
OK, using -O0, -Og, or -Os makes the code compile, -O1, -O2 or higher ICEs.
This looks fishy.
I'd prefer someone with better middle-end knowledge to look at it.
next prev parent reply other threads:[~2020-05-25 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 19:46 [Bug fortran/95323] New: " dcb314 at hotmail dot com
2020-05-25 20:38 ` [Bug fortran/95323] " anlauf at gcc dot gnu.org
2020-05-25 20:43 ` dcb314 at hotmail dot com
2020-05-25 20:46 ` dcb314 at hotmail dot com
2020-05-25 21:28 ` anlauf at gcc dot gnu.org [this message]
2020-05-26 7:16 ` [Bug tree-optimization/95323] " marxin 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-95323-4-ndzv4ht5mU@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: link
Be 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).