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 target/108140] ICE expanding __rbit
Date: Mon, 19 Dec 2022 11:19:51 +0000	[thread overview]
Message-ID: <bug-108140-4-wlYjKBle0V@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108140-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kyrylo Tkachov <ktkachov@gcc.gnu.org>:

https://gcc.gnu.org/g:98756bcbe27647f263f2b312d1d933d70cf56ba9

commit r13-4777-g98756bcbe27647f263f2b312d1d933d70cf56ba9
Author: Kyrylo Tkachov <kyrylo.tkachov@arm.com>
Date:   Mon Dec 19 11:16:47 2022 +0000

    aarch64: PR target/108140 Handle NULL target in data intrinsic expansion

    In this PR we ICE when expanding the __rbit builtin with a NULL target rtx.
    I *think* that only happens when the result is unused and hence maybe we
shouldn't be expanding
    any RTL at all, but the ICE here is easily fixed by deriving the mode from
the type of the expression
    rather than the target.

    This patch does that.
    Bootstrapped and tested on aarch64-none-linux-gnu.

    gcc/ChangeLog:

            PR target/108140
            * config/aarch64/aarch64-builtins.cc
            (aarch64_expand_builtin_data_intrinsic): Handle NULL target.

    gcc/testsuite/ChangeLog:

            PR target/108140
            * gcc.target/aarch64/acle/pr108140.c: New test.

  parent reply	other threads:[~2022-12-19 11:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16  8:18 [Bug c/108140] New: tzcnt gives different result in debug vs release levo.delellis at gmail dot com
2022-12-16  8:28 ` [Bug c/108140] " jakub at gcc dot gnu.org
2022-12-16  8:29 ` jakub at gcc dot gnu.org
2022-12-16  8:45 ` levo.delellis at gmail dot com
2022-12-16  9:35 ` [Bug middle-end/108140] ICE expanding __rbit amonakov at gcc dot gnu.org
2022-12-16 11:55 ` ktkachov at gcc dot gnu.org
2022-12-19 11:19 ` cvs-commit at gcc dot gnu.org [this message]
2023-01-10 10:26 ` [Bug target/108140] " cvs-commit at gcc dot gnu.org
2023-05-08 12:26 ` rguenth at gcc dot gnu.org
2023-05-09  9:04 ` ktkachov 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-108140-4-wlYjKBle0V@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).