public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/107307] [12/13 Regression] ICE tree check: expected class 'type', have 'exceptional' (error_mark) in canonicalize_component_ref, at gimplify.cc:2923 since r12-3278-g823685221de986af Date: Thu, 17 Nov 2022 20:24:40 +0000 [thread overview] Message-ID: <bug-107307-4-kIKd6aGA5K@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107307-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107307 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Simple fix: diff --git a/gcc/gimplify.cc b/gcc/gimplify.cc index f06ce3cc77a..bd772c15bec 100644 --- a/gcc/gimplify.cc +++ b/gcc/gimplify.cc @@ -3319,7 +3319,9 @@ gimplify_compound_lval (tree *expr_p, gimple_seq *pre_p, gimple_seq *post_p, } /* If the outermost expression is a COMPONENT_REF, canonicalize its type. */ - if ((fallback & fb_rvalue) && TREE_CODE (*expr_p) == COMPONENT_REF) + if (ret != GS_ERROR + && (fallback & fb_rvalue) + && TREE_CODE (*expr_p) == COMPONENT_REF) { canonicalize_component_ref (expr_p); } I am going to submit this and PR 106764 together.
next prev parent reply other threads:[~2022-11-17 20:24 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-18 17:44 [Bug c/107307] New: ICE tree check: expected class 'type', have 'exceptional' (error_mark) in canonicalize_component_ref, at gimplify.cc:2923 gscfq@t-online.de 2022-10-19 6:49 ` [Bug c/107307] ICE tree check: expected class 'type', have 'exceptional' (error_mark) in canonicalize_component_ref, at gimplify.cc:2923 since r12-3278-g823685221de986af marxin at gcc dot gnu.org 2022-10-19 7:19 ` [Bug middle-end/107307] [12/13 Regression] " rguenth at gcc dot gnu.org 2022-11-15 19:37 ` pinskia at gcc dot gnu.org 2022-11-17 20:24 ` pinskia at gcc dot gnu.org [this message] 2022-11-17 20:41 ` pinskia at gcc dot gnu.org 2022-11-18 17:03 ` cvs-commit at gcc dot gnu.org 2022-11-18 17:05 ` pinskia 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-107307-4-kIKd6aGA5K@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).