mirror of
git://gcc.gnu.org/git/gcc.git
synced 2025-04-07 01:40:39 +08:00
9ecb422126
pass_return_slot::execute has: /* Ignore internal functions without direct optabs, those are expanded specially and aggregate_value_p on their result might result in undesirable warnings with some backends. */ && (!gimple_call_internal_p (stmt) || direct_internal_fn_p (gimple_call_internal_fn (stmt))) && aggregate_value_p (TREE_TYPE (gimple_call_lhs (stmt)), gimple_call_fndecl (stmt))) But what the comment says applies to directly-mapped internal functions too, since they're only used if the target supports them without a libcall. This was triggering an ICE on the attached testcase. The svld3 call is folded to an IFN_LOAD_LANES, which returns an array of vectors with VNx48QImode. Since no such return type can exist in C, the target hook was complaining about an unexpected use of SVE modes. (And we want to keep asserting for that, so that we don't accidentally define an ABI for an unexpected corner case.) 2020-01-09 Richard Sandiford <richard.sandiford@arm.com> gcc/ * tree-nrv.c (pass_return_slot::execute): Handle all internal functions the same way, rather than singling out those that aren't mapped directly to optabs. gcc/testsuite/ * gcc.target/aarch64/sve/acle/general/nrv_1.c: New test. From-SVN: r280048
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.