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/103368] [11/12/13 Regression] ICE in gimplify_expr, at gimplify.c:15668 since r12-4464-g017665f63047ce47 Date: Tue, 02 Apr 2024 19:40:22 +0000 [thread overview] Message-ID: <bug-103368-4-YLBzIU04KR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103368-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103368 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |14.0 Summary|[11/12/13/14 Regression] |[11/12/13 Regression] ICE |ICE in gimplify_expr, at |in gimplify_expr, at |gimplify.c:15668 since |gimplify.c:15668 since |r12-4464-g017665f63047ce47 |r12-4464-g017665f63047ce47 --- Comment #4 from anlauf at gcc dot gnu.org --- Seems to ICE no longer at r14-9759, but 13-branch and older still fail. Adjusting summary. But is it really invalid code? Intel and NAG accept it.
next prev parent reply other threads:[~2024-04-02 19:40 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-22 19:40 [Bug fortran/103368] New: [11/12 Regression] ICE in gimplify_expr, at gimplify.c:15668 gscfq@t-online.de 2021-11-23 7:34 ` [Bug fortran/103368] " rguenth at gcc dot gnu.org 2021-11-23 7:59 ` [Bug fortran/103368] [11/12 Regression] ICE in gimplify_expr, at gimplify.c:15668 since r12-4464-g017665f63047ce47 marxin at gcc dot gnu.org 2021-11-23 8:03 ` pinskia at gcc dot gnu.org 2022-04-21 7:50 ` rguenth at gcc dot gnu.org 2023-05-29 10:06 ` [Bug fortran/103368] [11/12/13/14 " jakub at gcc dot gnu.org 2024-04-02 19:40 ` anlauf at gcc dot gnu.org [this message] 2024-04-03 0:49 ` [Bug fortran/103368] [11/12/13 " jvdelisle 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-103368-4-YLBzIU04KR@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).