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 c/100525] ICE: tree check: expected class ‘type’, have ‘exceptional’ (error_mark) in useless_type_conversion_p, at gimple-expr.c:87
Date: Tue, 09 Aug 2022 06:55:57 +0000	[thread overview]
Message-ID: <bug-100525-4-LwPBDV8922@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100525-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100525

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Btw, the issue for the original testcase is that we run into

static void
c_parser_gimple_statement (gimple_parser &parser, gimple_seq *seq)
{
...
  /* GIMPLE call statement without LHS.  */
  if (c_parser_next_token_is (parser, CPP_SEMICOLON)
      && TREE_CODE (lhs.value) == CALL_EXPR)
    {
      gimple *call;
      call = gimple_build_call_from_tree (lhs.value, NULL);
      gimple_seq_add_stmt_without_update (seq, call);
      gimple_set_location (call, loc);
      return;

and the C FE hands us back a non-error CALL_EXPR with an error_mark_node
argument.  Usually those get "cleaned out" during gimplification but here
it prevails.

  parent reply	other threads:[~2022-08-09  6:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-11 15:24 [Bug c/100525] New: " cnsun at uwaterloo dot ca
2021-08-12 22:22 ` [Bug c/100525] " pinskia at gcc dot gnu.org
2022-08-08 12:37 ` k.even-mendoza at imperial dot ac.uk
2022-08-08 15:47 ` pinskia at gcc dot gnu.org
2022-08-09  6:55 ` rguenth at gcc dot gnu.org [this message]
2022-11-15 19:44 ` pinskia at gcc dot gnu.org
2022-11-28 22:20 ` 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-100525-4-LwPBDV8922@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: link
Be 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).