mirror of
https://github.com/gcc-mirror/gcc.git
synced 2026-05-06 23:14:49 +02:00
08cdd61e70
commit g:1786be14e94bf1a7806b9dc09186f021737f0227 stops storing in STMT_VINFO_VECTYPE the vectype of the current stmt being vectorized and instead requires the use of SLP_TREE_VECTYPE for everything but data-refs. However contrary to what the commit says not all usages of STMT_VINFO_VECTYPE have been purged from vectorizable_* as the costing hooks which don't pass the SLP tree as an agrument will extract vectype using STMT_VINFO_VECTYPE. This results in no vector type being passed to the backends and results in a few costing test failures in AArch64. This commit replaces the last few cases I could find, all except for in vectorizable_reduction when single_defuse_cycle where the stmt being costed is not the representative of the PHI in the SLP tree but rather the out of tree reduction statement. So I've left that alone, but it does mean vectype is NULL. Most likely this needs to use the overload where we pass an explicit vectype but I wasn't sure so left it for now. gcc/ChangeLog: PR target/121536 * tree-vect-loop.cc (vectorizable_phi, vectorizable_recurr, vectorizable_nonlinear_induction, vectorizable_induction): Pass slp_node instead of stmt_info to record_stmt_cost.
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.