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 middle-end/108546] [11/12/13 Regression] ICE in expand_expr_real_1, at expr.cc:10910 since r10-4531-ga2c26c50310a3363 Date: Tue, 21 Feb 2023 12:56:24 +0000 [thread overview] Message-ID: <bug-108546-4-54VtWDSQI1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108546-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108546 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|fortran |middle-end Priority|P3 |P2 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- (gdb) p exp $1 = <parm_decl 0x7ffff7ff3280 x> (gdb) p context $2 = <function_decl 0x7ffff6460f00 s> (gdb) p current_function_decl $3 = <function_decl 0x7ffff6065200 __m_MOD_s._omp_fn.0> so we somehow forgot to remap 's'? Looks like a middle-end issue to me.
next prev parent reply other threads:[~2023-02-21 12:56 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-25 17:52 [Bug fortran/108546] New: [11/12/13 Regression] ICE in expand_expr_real_1, at expr.cc:10910 gscfq@t-online.de 2023-01-26 7:44 ` [Bug fortran/108546] " rguenth at gcc dot gnu.org 2023-01-26 9:43 ` [Bug fortran/108546] [11/12/13 Regression] ICE in expand_expr_real_1, at expr.cc:10910 since r10-4531-ga2c26c50310a3363 marxin at gcc dot gnu.org 2023-02-21 12:56 ` rguenth at gcc dot gnu.org [this message] 2023-03-01 12:53 ` [Bug middle-end/108546] " cvs-commit at gcc dot gnu.org 2023-03-08 10:55 ` cvs-commit at gcc dot gnu.org 2023-03-09 11:10 ` cvs-commit at gcc dot gnu.org 2023-03-09 11:11 ` burnus 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-108546-4-54VtWDSQI1@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).