Go to file
Tamar Christina d1965b1fd8 AArch64: Extend intrinsics framework to account for merging predications without gp [PR121604]
In PR121604 the problem was noted that currently the SVE intrinsics
infrastructure assumes that for any predicated operation that the GP is at the
first argument position which has a svbool_t or for a unary merging operation
that it's in the second position.

However you have intrinsics like fmov_lane which have an svbool_t but it's not
a GP but instead it's the inactive lanes.

You also have instructions like BRKB which work only on predicates so it
incorrectly determines the first operand to be the GP, while that's also the
inactive lanes.

However during apply_predication we do have the information about where the GP
is.  This patch re-organizes the code to record this information into the
function_instance such that folders have access to this information.

For functions that are outliers like pmov_lane we can now override the
availability of the intrinsics having a GP.

gcc/ChangeLog:

	PR target/121604
	* config/aarch64/aarch64-sve-builtins-shapes.cc (apply_predication):
	Store gp_index.
	(struct pmov_to_vector_lane_def): Mark instruction as has no GP.
	* config/aarch64/aarch64-sve-builtins.h (function_instance::gp_value,
	function_instance::inactive_values, function_instance::gp_index,
	function_shape::has_gp_argument_p): New.
	* config/aarch64/aarch64-sve-builtins.cc (gimple_folder::fold_pfalse):
	Simplify code and use GP helpers.

gcc/testsuite/ChangeLog:

	PR target/121604
	* gcc.target/aarch64/sve/pr121604_brk.c: New test.
	* gcc.target/aarch64/sve2/pr121604_pmov.c: New test.

Co-authored-by: Jennifer Schmitz <jschmitz@nvidia.com>
2025-10-17 15:43:10 +01:00
.forgejo
.github
INSTALL
c++tools
config
contrib Daily bump. 2025-10-17 00:18:48 +00:00
fixincludes
gcc AArch64: Extend intrinsics framework to account for merging predications without gp [PR121604] 2025-10-17 15:43:10 +01:00
gnattools
gotools
include Daily bump. 2025-10-17 00:18:48 +00:00
libada
libatomic Daily bump. 2025-10-10 00:21:51 +00:00
libbacktrace
libcc1 Daily bump. 2025-10-10 00:21:51 +00:00
libcody
libcpp Daily bump. 2025-10-14 00:20:06 +00:00
libdecnumber
libffi
libgcc Daily bump. 2025-10-10 00:21:51 +00:00
libgcobol Daily bump. 2025-10-11 00:21:09 +00:00
libgfortran
libgm2
libgo
libgomp Daily bump. 2025-10-17 00:18:48 +00:00
libgrust
libiberty
libitm
libobjc
libphobos
libquadmath
libsanitizer
libssp
libstdc++-v3 libstdc++: Fix typo in in __atomic_ref_base::_S_required_alignment. 2025-10-17 10:26:26 +02:00
libvtv
lto-plugin
maintainer-scripts
zlib
.b4-config
.dir-locals.el
.editorconfig
.gitattributes
.gitignore
ABOUT-NLS
COPYING
COPYING.LIB
COPYING.RUNTIME
COPYING3
COPYING3.LIB
ChangeLog Daily bump. 2025-10-16 00:21:56 +00:00
ChangeLog.jit
ChangeLog.tree-ssa
MAINTAINERS
Makefile.def PR81358: Enable automatic linking of libatomic. 2025-10-09 07:26:51 +00:00
Makefile.in [PATCH] Makefile.tpl: remove an extra \; from find command 2025-10-15 11:32:21 -06:00
Makefile.tpl [PATCH] Makefile.tpl: remove an extra \; from find command 2025-10-15 11:32:21 -06:00
README
SECURITY.txt
ar-lib
compile
config-ml.in *: Fix patch email address 2025-10-11 11:08:01 +02:00
config.guess
config.rpath
config.sub
configure PR81358: Enable automatic linking of libatomic. 2025-10-09 07:26:51 +00:00
configure.ac PR81358: Enable automatic linking of libatomic. 2025-10-09 07:26:51 +00:00
depcomp
install-sh
libtool-ldflags
libtool.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
lt~obsolete.m4
missing
mkdep
mkinstalldirs
move-if-change
multilib.am
symlink-tree *: Fix patch email address 2025-10-11 11:08:01 +02:00
test-driver
ylwrap

README

This directory contains the GNU Compiler Collection (GCC).

The GNU Compiler Collection is free software.  See the files whose
names start with COPYING for copying permission.  The manuals, and
some of the runtime libraries, are under different terms; see the
individual source files for details.

The directory INSTALL contains copies of the installation information
as HTML and plain text.  The source of this information is
gcc/doc/install.texi.  The installation information includes details
of what is included in the GCC sources and what files GCC installs.

See the file gcc/doc/gcc.texi (together with other files that it
includes) for usage and porting information.  An online readable
version of the manual is in the files gcc/doc/gcc.info*.

See http://gcc.gnu.org/bugs/ for how to report bugs usefully.

Copyright years on GCC source files may be listed using range
notation, e.g., 1987-2012, indicating that every year in the range,
inclusive, is a copyrightable year that could otherwise be listed
individually.