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 c/106764] [12/13 Regression] ICE on invalid code in tree check: expected function_type or method_type, have error_mark in gimplify_call_expr, at gimplify.cc Date: Thu, 17 Nov 2022 20:21:59 +0000 [thread overview] Message-ID: <bug-106764-4-WrLnoQVstf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106764-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106764 --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Actually the fix is just check the return value of gimplify_expr to make sure it was not GS_ERROR. diff --git a/gcc/gimplify.cc b/gcc/gimplify.cc index f06ce3cc77a..9b74f957308 100644 --- a/gcc/gimplify.cc +++ b/gcc/gimplify.cc @@ -3709,6 +3709,9 @@ gimplify_call_expr (tree *expr_p, gimple_seq *pre_p, bool want_value) ret = gimplify_expr (&CALL_EXPR_FN (*expr_p), pre_p, NULL, is_gimple_call_addr, fb_rvalue); + if (ret == GS_ERROR) + return GS_ERROR; + nargs = call_expr_nargs (*expr_p); /* Get argument types for verification. */
next prev parent reply other threads:[~2022-11-17 20:21 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-28 15:10 [Bug c/106764] New: " k.even-mendoza at imperial dot ac.uk 2022-08-28 15:51 ` [Bug c/106764] " pinskia at gcc dot gnu.org 2022-08-29 8:36 ` rguenth at gcc dot gnu.org 2022-08-29 13:41 ` marxin at gcc dot gnu.org 2022-10-22 0:13 ` [Bug c/106764] [12/13 Regression] " pinskia at gcc dot gnu.org 2022-11-15 19:37 ` pinskia at gcc dot gnu.org 2022-11-17 20:06 ` pinskia at gcc dot gnu.org 2022-11-17 20:21 ` pinskia at gcc dot gnu.org [this message] 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-106764-4-WrLnoQVstf@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).