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/114156] during GIMPLE pass: bitintlower ICE: in lower_stmt, at gimple-lower-bitint.cc:5335 with -O -m32 and _BitInt(128) __builtin_memmove()
Date: Fri, 01 Mar 2024 10:07:22 +0000	[thread overview]
Message-ID: <bug-114156-4-GJIGh0Qf2Z@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114156-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 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:d3d0fcb652748191714e4c0b2541e977a7fc7bd7

commit r14-9248-gd3d0fcb652748191714e4c0b2541e977a7fc7bd7
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Mar 1 11:04:51 2024 +0100

    bitint: Handle VCE from large/huge _BitInt SSA_NAME from load [PR114156]

    When adding checks in which case not to merge a VIEW_CONVERT_EXPR from
    large/huge _BitInt to vector/complex etc., I missed the case of loads.
    Those are handled differently later.
    Anyway, I think the load case is something we can handle just fine,
    so the following patch does that instead of preventing the merging
    gimple_lower_bitint; we'd then copy from memory to memory and and do the
    vce only on the second one, it is just better to vce the first one.

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

            PR middle-end/114156
            * gimple-lower-bitint.cc (bitint_large_huge::lower_stmt): Allow
            rhs1 of a VCE to have no underlying variable if it is a load and
            handle that case.

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

  parent reply	other threads:[~2024-03-01 10:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28 17:28 [Bug middle-end/114156] New: " zsojka at seznam dot cz
2024-02-29 18:51 ` [Bug middle-end/114156] " jakub at gcc dot gnu.org
2024-03-01 10:07 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-01 10:15 ` 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-114156-4-GJIGh0Qf2Z@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).