mirror of
git://gcc.gnu.org/git/gcc.git
synced 2025-04-02 07:30:27 +08:00
3e2751ce55
The Advanced SIMD and SVE permute patterns both split the permute operation into a base name and a hilo suffix. That works well, but it means that for "@" patterns, we need to pass the permute code twice, once for the base name and once for the suffix. Having a unified name avoids that and also makes the definitions slightly simpler. 2019-08-13 Richard Sandiford <richard.sandiford@arm.com> gcc/ * config/aarch64/iterators.md (perm_insn): Include the "1"/"2" suffix. (perm_hilo): Remove UNSPEC_ZIP*, UNSEPC_TRN* and UNSPEC_UZP*. * config/aarch64/aarch64-simd.md (aarch64_<PERMUTE:perm_insn><PERMUTE:perm_hilo><mode>): Rename to.. (aarch64_<PERMUTE:perm_insn><mode>): ...this and remove perm_hilo from the asm template. * config/aarch64/aarch64-sve.md (aarch64_<perm_insn><perm_hilo><PRED_ALL:mode>): Rename to.. (aarch64_<perm_insn><PRED_ALL:mode>): ...this and remove perm_hilo from the asm template. (aarch64_<perm_insn><perm_hilo><SVE_ALL:mode>): Rename to.. (aarch64_<perm_insn><SVE_ALL:mode>): ...this and remove perm_hilo from the asm template. * config/aarch64/aarch64-simd-builtins.def: Update comment. From-SVN: r274366
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.