public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/113406] ICE: tree check: expected class 'type', have 'exceptional' (error_mark) in useless_type_conversion_p, at gimple-expr.cc:85 with -fstrub=internal and _BitInt() (and __GIMPLE with _BitInt return)
Date: Wed, 17 Jan 2024 12:57:39 +0000	[thread overview]
Message-ID: <bug-113406-4-ElZMZT8PRx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113406-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:2c74d5c0a0f21ae1d0c195ca0d81a3d1032f27e3

commit r14-8183-g2c74d5c0a0f21ae1d0c195ca0d81a3d1032f27e3
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed Jan 17 13:54:44 2024 +0100

    ipa-strub: Fix handling of _BitInt returns [PR113406]

    Seems pass_ipa_strub::execute contains a copy of the expand_thunk
    code I've changed for _BitInt in r14-6805 PR112941 - larger _BitInts
    are aggregate_value_p even when they are is_gimple_reg_type.

    2024-01-17  Jakub Jelinek  <jakub@redhat.com>

            PR middle-end/113406
            * ipa-strub.cc (pass_ipa_strub::execute): Check aggregate_value_p
            regardless of whether is_gimple_reg_type (restype) or not.

            * gcc.dg/bitint-70.c: New test.

  parent reply	other threads:[~2024-01-17 12:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 19:58 [Bug tree-optimization/113406] New: ICE: tree check: expected class 'type', have 'exceptional' (error_mark) in useless_type_conversion_p, at gimple-expr.cc:85 with -fstrub=internal and _BitInt() zsojka at seznam dot cz
2024-01-15 23:41 ` [Bug middle-end/113406] " pinskia at gcc dot gnu.org
2024-01-16  8:38 ` [Bug middle-end/113406] ICE: tree check: expected class 'type', have 'exceptional' (error_mark) in useless_type_conversion_p, at gimple-expr.cc:85 with -fstrub=internal and _BitInt() (and __GIMPLE with _BitInt return) jakub at gcc dot gnu.org
2024-01-16 11:05 ` jakub at gcc dot gnu.org
2024-01-16 14:48 ` pinskia at gcc dot gnu.org
2024-01-16 14:52 ` jakub at gcc dot gnu.org
2024-01-17 12:57 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-17 12:58 ` jakub at gcc dot gnu.org
2024-01-20 17:10 ` 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-113406-4-ElZMZT8PRx@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).