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 fortran/84779] [10/11/12/13 Regression] Compiling gfortran.fortran-torture/execute/entry_4.f90 with -O1 or -Os and -fdefault-integer-8 gives an ICE Date: Thu, 30 Mar 2023 19:10:37 +0000 [thread overview] Message-ID: <bug-84779-4-NaSSpmNOJM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-84779-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84779 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC|anlauf at gmx dot de |anlauf at gcc dot gnu.org --- Comment #13 from anlauf at gcc dot gnu.org --- I've come back to this PR again and spent a while trying to further narrow things down and to find the gcc options that make the code compile or fail. Minimal reproducer: complex function f2 (a) implicit none integer a logical e2 entry e2 (a) if (a > 0) then e2 = .true. else f2 = 45 endif end Basic command line: "gfortran -fdefault-integer-8", plus: these all lead to an ICE: ! -O1 ! -O1 -fno-tree-pre ! -O2 -fno-tree-pre but no ICE with: ! -O2 ! -O1 -ftree-pre ! -O2 -ftree-pre ! -O1 -fno-tree-sra ! -O2 -fno-tree-sra ! -O1 -fno-tree-sra -fno-tree-pre ! -O2 -fno-tree-sra -fno-tree-pre So is this now a frontend bug - what could it be? - or a middle-end issue?
next prev parent reply other threads:[~2023-03-30 19:10 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-84779-4@http.gcc.gnu.org/bugzilla/> 2021-05-14 9:50 ` [Bug fortran/84779] [9/10/11/12 " jakub at gcc dot gnu.org 2021-06-01 8:10 ` rguenth at gcc dot gnu.org 2022-05-27 9:38 ` [Bug fortran/84779] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:34 ` jakub at gcc dot gnu.org 2023-03-30 19:10 ` anlauf at gcc dot gnu.org [this message] 2023-07-07 10:33 ` [Bug fortran/84779] [11/12/13/14 " 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-84779-4-NaSSpmNOJM@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).