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/112770] during GIMPLE pass: bitintlower0 ICE: verify_gimple failed: statement marked for throw in middle of block with -fnon-call-exceptions and _BitInt(128)
Date: Fri, 01 Dec 2023 09:57:27 +0000	[thread overview]
Message-ID: <bug-112770-4-HizU3hfLgq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112770-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 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:b1fe98dee21773b9d908469effe2580567b903fb

commit r14-6051-gb1fe98dee21773b9d908469effe2580567b903fb
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Dec 1 10:56:52 2023 +0100

    lower-bitint: Fix lowering of middle sized _BitInt operations which can
throw [PR112770]

    The middle kind _BitInt lowering is mostly done by casting the BITINT_TYPE
    operands (if any) to a signed/unsigned integer type which has larger/equal
    precision, using such integer type also for the lhs (if BITINT_TYPE) and
    and adding a cast after the statement from that new lhs to the old
    (BITINT_TYPE) lhs.  Note, for middle kind this isn't done for GIMPLE_CALLs.
    Most of the time that works nicely, the exception as the following testcase
    shows is -fnon-call-exceptions and some operations which can trap.  Because
    inserting the cast to a new lhs after the statement results in a trapping
    statement in the middle of a basic block.
    The following patch fixes that by emitting the cast on the fallthru edge
    instead.

    2023-12-01  Jakub Jelinek  <jakub@redhat.com>

            PR middle-end/112770
            * gimple-lower-bitint.cc (gimple_lower_bitint): When adjusting
            lhs of middle _BitInt setter which ends bb, insert cast on
            the fallthru edge rather than after stmt.

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

  reply	other threads:[~2023-12-01  9:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 19:55 [Bug middle-end/112770] New: " zsojka at seznam dot cz
2023-12-01  9:57 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-01  9:58 ` [Bug middle-end/112770] " jakub 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-112770-4-HizU3hfLgq@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).