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/110725] [13/14 Regression] internal compiler error: in expand_expr_real_1, at expr.cc:10897 Date: Tue, 18 Jul 2023 17:56:56 +0000 [thread overview] Message-ID: <bug-110725-4-ij9YzL0P7A@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110725-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110725 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Summary|internal compiler error: in |[13/14 Regression] internal |expand_expr_real_1, at |compiler error: in |expr.cc:10897 |expand_expr_real_1, at | |expr.cc:10897 Target Milestone|--- |13.2 Keywords| |ice-on-valid-code, openmp Last reconfirmed| |2023-07-18 Priority|P3 |P4 --- Comment #1 from anlauf at gcc dot gnu.org --- The code is accepted by Nvidia. No ICE at -O0, but ICE at -Og, -O1, and higher. ICE confirmed also on x86_64, so likely not target-specific.
next prev parent reply other threads:[~2023-07-18 17:56 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-18 17:22 [Bug fortran/110725] New: " tonycurtis32 at gmail dot com 2023-07-18 17:56 ` anlauf at gcc dot gnu.org [this message] 2023-07-18 18:55 ` [Bug fortran/110725] [13/14 Regression,openmp] " kargl at gcc dot gnu.org 2023-07-19 6:47 ` [Bug fortran/110725] [13/14 Regression] " rguenth at gcc dot gnu.org 2023-07-19 17:44 ` kargl at gcc dot gnu.org 2023-07-24 15:04 ` jakub at gcc dot gnu.org 2023-07-24 20:58 ` cvs-commit at gcc dot gnu.org 2023-07-25 13:45 ` cvs-commit at gcc dot gnu.org 2023-07-27 9:27 ` rguenth at gcc dot gnu.org 2023-07-27 16:17 ` cvs-commit at gcc dot gnu.org 2024-03-04 4:54 ` law 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-110725-4-ij9YzL0P7A@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).