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/100532] ICE: tree check: expected class ‘type’, have ‘exceptional’ (error_mark) in useless_type_conversion_p, at gimple-expr.c:259 Date: Thu, 19 Oct 2023 05:30:25 +0000 [thread overview] Message-ID: <bug-100532-4-DIWwbkKvPv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100532-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100532 --- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Maybe the simple fix: diff --git a/gcc/c/c-typeck.cc b/gcc/c/c-typeck.cc index 6e044b4afbc..8f8562936dc 100644 --- a/gcc/c/c-typeck.cc +++ b/gcc/c/c-typeck.cc @@ -3367,7 +3367,7 @@ convert_argument (location_t ploc, tree function, tree fundecl, { error_at (ploc, "type of formal parameter %d is incomplete", parmnum + 1); - return val; + return error_mark_node; } /* Optionally warn about conversions that differ from the default
next prev parent reply other threads:[~2023-10-19 5:30 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-11 16:06 [Bug c/100532] New: " cnsun at uwaterloo dot ca 2021-05-11 16:10 ` [Bug c/100532] " cnsun at uwaterloo dot ca 2021-05-12 9:29 ` marxin at gcc dot gnu.org 2021-08-22 4:39 ` [Bug c/100532] [12 Regression] " pinskia at gcc dot gnu.org 2021-08-22 4:40 ` pinskia at gcc dot gnu.org 2021-08-22 13:51 ` [Bug c/100532] " hjl.tools at gmail dot com 2022-05-06 8:30 ` jakub at gcc dot gnu.org 2022-11-15 19:45 ` pinskia at gcc dot gnu.org 2023-04-23 3:01 ` pinskia at gcc dot gnu.org 2023-10-18 3:25 ` pinskia at gcc dot gnu.org 2023-10-19 5:30 ` pinskia at gcc dot gnu.org [this message] 2023-10-19 15:39 ` pinskia at gcc dot gnu.org 2023-10-19 16:51 ` cvs-commit at gcc dot gnu.org 2023-10-19 16:52 ` 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-100532-4-DIWwbkKvPv@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).