public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/106126] New: tree check fail in useless_type_conversion_p, at gimple-expr.cc:87
Date: Tue, 28 Jun 2022 17:46:12 +0000	[thread overview]
Message-ID: <bug-106126-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 106126
           Summary: tree check fail in useless_type_conversion_p, at
                    gimple-expr.cc:87
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

Created attachment 53218
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53218&action=edit
C source code

For the attached C code, with recent gcc trunk and compiler flag -O2, I get

$ ../results/bin/gcc -c -O2 bug822.c
during GIMPLE pass: iftoswitch
/home/dcb36/rpmbuild/BUILD/libsolv-0.7.20/src/conda.c: In function
‘pool_conda_matchspec’:
/home/dcb36/rpmbuild/BUILD/libsolv-0.7.20/src/conda.c:679:1: internal compiler
error: tree check: expected class ‘type’, have ‘exceptional’ (error_mark) in
useless_type_conversion_p, at gimple-expr.cc:87
  679 | }
      | ^
0x10fcfba tree_class_check_failed(tree_node const*, tree_code_class, char
const*, int, char const*)
        ../../trunk.git/gcc/tree.cc:8866
0x9ffd8c tree_class_check(tree_node*, tree_code_class, char const*, int, char
const*)
        ../../trunk.git/gcc/tree.h:3639
0x9ffd8c useless_type_conversion_p(tree_node*, tree_node*)
        ../../trunk.git/gcc/gimple-expr.cc:87

I will have my usual go at identifying a git hash range and reducing the code.

             reply	other threads:[~2022-06-28 17:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 17:46 dcb314 at hotmail dot com [this message]
2022-06-28 17:51 ` [Bug tree-optimization/106126] " dcb314 at hotmail dot com
2022-06-28 17:59 ` dcb314 at hotmail dot com
2022-06-28 20:06 ` dcb314 at hotmail dot com
2022-06-28 20:46 ` dcb314 at hotmail dot com
2022-06-28 21:33 ` dcb314 at hotmail dot com
2022-06-29  9:47 ` rguenth at gcc dot gnu.org
2022-06-29 11:45 ` dcb314 at hotmail dot com
2022-06-29 11:53 ` dcb314 at hotmail dot com
2022-06-29 11:59 ` [Bug tree-optimization/106126] [12 Regression] tree check fail in useless_type_conversion_p, at gimple-expr.cc:87 since r13-1184-g57424087e82db140 marxin at gcc dot gnu.org
2022-06-29 12:00 ` marxin at gcc dot gnu.org
2022-06-30  2:21 ` luoxhu at gcc dot gnu.org
2022-06-30  2:37 ` luoxhu at gcc dot gnu.org
2022-06-30  3:34 ` luoxhu at gcc dot gnu.org
2022-06-30 13:03 ` marxin at gcc dot gnu.org
2022-06-30 19:52 ` dcb314 at hotmail dot com
2022-07-01  6:48 ` cvs-commit at gcc dot gnu.org
2022-07-01  6:48 ` [Bug tree-optimization/106126] [13 " marxin at gcc dot gnu.org
2022-07-01  6:54 ` marxin at gcc dot gnu.org
2022-07-01  7:16 ` dcb314 at hotmail dot com
2022-07-01 17:48 ` dcb314 at hotmail dot com
2022-07-04 11:33 ` marxin 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-106126-4@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).