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/113988] during GIMPLE pass: bitintlower: internal compiler error: in lower_stmt, at gimple-lower-bitint.cc:5470
Date: Wed, 28 Feb 2024 08:55:10 +0000	[thread overview]
Message-ID: <bug-113988-4-oo2CMM7a5p@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113988-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #28 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:cc383e9702897dd783657ea3dce4aecf48318441

commit r14-9203-gcc383e9702897dd783657ea3dce4aecf48318441
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed Feb 28 09:40:15 2024 +0100

    gimple-fold: Use bitwise vector types rather than barely supported huge
integral types in memcpy etc. folding [PR113988]

    The following patch changes the memcpy etc. folding to use bitwise vector
    types rather  than huge INTEGER_TYPEs for copying of > MAX_FIXED_MODE_SIZE
    lengths.  The problem with the huge INTEGER_TYPEs is that they aren't
    supported very much, usually there are just optabs to handle moves of them,
    perhaps misaligned moves and that is it, so they pose problems e.g. to
    BITINT_TYPE lowering.

    2024-02-28  Jakub Jelinek  <jakub@redhat.com>

            PR tree-optimization/113988
            * stor-layout.h (bitwise_mode_for_size): Declare.
            * stor-layout.cc (bitwise_mode_for_size): New function.
            * gimple-fold.cc (gimple_fold_builtin_memory_op): Use it.
            Use bitwise_type_for_mode instead of
build_nonstandard_integer_type.
            Use BITS_PER_UNIT instead of 8.

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

  parent reply	other threads:[~2024-02-28  8:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19  9:51 [Bug c++/113988] New: " janschultke at googlemail dot com
2024-02-19 10:00 ` [Bug middle-end/113988] " pinskia at gcc dot gnu.org
2024-02-19 10:01 ` janschultke at googlemail dot com
2024-02-19 10:05 ` jakub at gcc dot gnu.org
2024-02-19 14:22 ` rguenth at gcc dot gnu.org
2024-02-19 14:30 ` rguenth at gcc dot gnu.org
2024-02-19 14:34 ` rguenth at gcc dot gnu.org
2024-02-19 14:34 ` jakub at gcc dot gnu.org
2024-02-19 14:37 ` rguenth at gcc dot gnu.org
2024-02-19 14:39 ` rguenth at gcc dot gnu.org
2024-02-19 14:40 ` jakub at gcc dot gnu.org
2024-02-19 14:42 ` jakub at gcc dot gnu.org
2024-02-19 14:44 ` rguenther at suse dot de
2024-02-19 15:35 ` hjl.tools at gmail dot com
2024-02-19 18:57 ` jakub at gcc dot gnu.org
2024-02-20  7:32 ` rguenth at gcc dot gnu.org
2024-02-20  9:12 ` rsandifo at gcc dot gnu.org
2024-02-21 12:40 ` jakub at gcc dot gnu.org
2024-02-21 12:50 ` jakub at gcc dot gnu.org
2024-02-22  7:47 ` rguenther at suse dot de
2024-02-22  8:10 ` jakub at gcc dot gnu.org
2024-02-22  8:34 ` rguenther at suse dot de
2024-02-22  8:37 ` jakub at gcc dot gnu.org
2024-02-22  8:52 ` rguenther at suse dot de
2024-02-23 10:06 ` jakub at gcc dot gnu.org
2024-02-24 11:46 ` jakub at gcc dot gnu.org
2024-02-25 18:37 ` zsojka at seznam dot cz
2024-02-26 21:41 ` zsojka at seznam dot cz
2024-02-27 11:53 ` jakub at gcc dot gnu.org
2024-02-28  8:55 ` cvs-commit at gcc dot gnu.org [this message]
2024-02-28  9:01 ` 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-113988-4-oo2CMM7a5p@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).