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/115464] [14 Backport] ICE when building libaom on arm64 (neon sve bridge usage with tbl/perm)
Date: Tue, 18 Jun 2024 11:23:12 +0000 [thread overview]
Message-ID: <bug-115464-4-CNpwRQjfMX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115464-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115464
--- Comment #12 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Richard Sandiford <rsandifo@gcc.gnu.org>:
https://gcc.gnu.org/g:6bd4fbae45d11795a9a6f54b866308d4d7134def
commit r15-1399-g6bd4fbae45d11795a9a6f54b866308d4d7134def
Author: Richard Sandiford <richard.sandiford@arm.com>
Date: Tue Jun 18 12:22:31 2024 +0100
aarch64: Add some uses of force_lowpart_subreg
This patch makes more use of force_lowpart_subreg, similarly
to the recent patch for force_subreg. The criteria were:
(1) The code is obviously specific to expand (where new pseudos
can be created).
(2) The value is obviously an rvalue rather than an lvalue.
gcc/
PR target/115464
* config/aarch64/aarch64-builtins.cc (aarch64_expand_fcmla_builtin)
(aarch64_expand_rwsr_builtin): Use force_lowpart_subreg instead of
simplify_gen_subreg and lowpart_subreg.
* config/aarch64/aarch64-sve-builtins-base.cc
(svset_neonq_impl::expand): Likewise.
* config/aarch64/aarch64-sve-builtins-sme.cc
(add_load_store_slice_operand): Likewise.
* config/aarch64/aarch64.cc (aarch64_sve_reinterpret): Likewise.
(aarch64_addti_scratch_regs, aarch64_subvti_scratch_regs):
Likewise.
gcc/testsuite/
PR target/115464
* gcc.target/aarch64/sve/acle/general/pr115464_2.c: New test.
prev parent reply other threads:[~2024-06-18 11:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 15:50 [Bug target/115464] New: ICE when building libaom on arm64 sjames at gcc dot gnu.org
2024-06-12 15:50 ` [Bug target/115464] " sjames at gcc dot gnu.org
2024-06-12 15:50 ` sjames at gcc dot gnu.org
2024-06-12 17:44 ` [Bug target/115464] ICE when building libaom on arm64 (neon sve bridge usage with tbl/perm) tnfchris at gcc dot gnu.org
2024-06-12 19:04 ` tnfchris at gcc dot gnu.org
2024-06-12 20:05 ` rsandifo at gcc dot gnu.org
2024-06-13 3:17 ` tnfchris at gcc dot gnu.org
2024-06-13 3:21 ` tnfchris at gcc dot gnu.org
2024-06-13 11:48 ` cvs-commit at gcc dot gnu.org
2024-06-13 11:50 ` [Bug target/115464] [14 Backport] " rsandifo at gcc dot gnu.org
2024-06-13 17:24 ` tnfchris at gcc dot gnu.org
2024-06-14 6:45 ` rsandifo at gcc dot gnu.org
2024-06-18 11:23 ` cvs-commit at gcc dot gnu.org [this message]
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-115464-4-CNpwRQjfMX@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).