Go to file
Tamar Christina dbc38dd9e9 middle-end: Pass along SLP node when costing vector loads/stores
With the support to SLP only we now pass the VMAT through the SLP node, however
the majority of the costing calls inside vectorizable_load and
vectorizable_store do no pass the SLP node along.  Due to this the backend costing
never sees the VMAT for these cases anymore.

Additionally the helper around record_stmt_cost when both SLP and stmt_vinfo are
passed would only pass the SLP node along.  However the SLP node doesn't contain
all the info available in the stmt_vinfo and we'd have to go through the
SLP_TREE_REPRESENTATIVE anyway.  As such I changed the function to just Always
pass both along.  Unlike the VMAT changes, I don't believe there to be a
correctness issue here but would minimize the number of churn in the backend
costing until vectorizer costing as a whole is revisited in GCC 16.

These changes re-enable the cost model on AArch64 and also correctly find the
VMATs on loads and stores fixing testcases such as sve_iters_low_2.c.

gcc/ChangeLog:

	* tree-vect-data-refs.cc (vect_get_data_access_cost): Pass NULL for SLP
	node.
	* tree-vect-stmts.cc (record_stmt_cost): Expose.
	(vect_get_store_cost, vect_get_load_cost): Extend with SLP node.
	(vectorizable_store, vectorizable_load): Pass SLP node to all costing.
	* tree-vectorizer.h (record_stmt_cost): Always pass both SLP node and
	stmt_vinfo to costing.
	(vect_get_load_cost, vect_get_store_cost): Extend with SLP node.
2024-11-21 12:49:35 +00:00
.forgejo
.github
c++tools
config
contrib Daily bump. 2024-11-19 00:19:52 +00:00
fixincludes
gcc middle-end: Pass along SLP node when costing vector loads/stores 2024-11-21 12:49:35 +00:00
gnattools
gotools
include include: Add new post-DWARF 5 DW_LANG_* enumerators 2024-11-21 10:17:03 +01:00
INSTALL
libada
libatomic Daily bump. 2024-11-19 00:19:52 +00:00
libbacktrace
libcc1
libcody
libcpp Daily bump. 2024-11-19 00:19:52 +00:00
libdecnumber
libffi
libgcc Daily bump. 2024-11-20 00:19:59 +00:00
libgfortran
libgm2 Daily bump. 2024-11-21 00:20:27 +00:00
libgo
libgomp libgomp: testsuite: Fix libgomp.c/alloc-pinned-3.c etc. for C23 on non-Linux 2024-11-21 11:46:36 +01:00
libgrust
libiberty Daily bump. 2024-11-20 00:19:59 +00:00
libitm Daily bump. 2024-11-19 00:19:52 +00:00
libobjc
libphobos Daily bump. 2024-11-19 00:19:52 +00:00
libquadmath
libsanitizer
libssp
libstdc++-v3 Daily bump. 2024-11-21 00:20:27 +00:00
libvtv Daily bump. 2024-11-19 00:19:52 +00:00
lto-plugin
maintainer-scripts
zlib
.b4-config
.dir-locals.el
.gitattributes
.gitignore
ABOUT-NLS
ar-lib
ChangeLog Daily bump. 2024-11-20 00:19:59 +00:00
ChangeLog.jit
ChangeLog.tree-ssa
compile
config-ml.in
config.guess
config.rpath
config.sub
configure Add libdiagnostics (v4) 2024-11-18 17:08:36 -05:00
configure.ac Add libdiagnostics (v4) 2024-11-18 17:08:36 -05:00
COPYING
COPYING3
COPYING3.LIB
COPYING.LIB
COPYING.RUNTIME
depcomp
install-sh
libtool-ldflags
libtool.m4
lt~obsolete.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
MAINTAINERS
Makefile.def
Makefile.in
Makefile.tpl
missing
mkdep
mkinstalldirs
move-if-change
multilib.am
README
SECURITY.txt Remove Debian from SECURITY.txt 2024-11-19 12:27:33 +01:00
symlink-tree
test-driver
ylwrap

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.