mirror of
git://gcc.gnu.org/git/gcc.git
synced 2025-04-07 07:00:25 +08:00
915d28fe74
aarch64-sve.md was getting a bit jumbled, with related operations separated by unrelated operations. Also, many SVE instructions need to have several patterns due to the various ways in which predication can be used, and it was getting hard to tell which instructions had a complete set of patterns. This patch therefore tries to use an explicit grouping scheme. Banner comments are usually frowned on, but md files have been a traditional exception (e.g. when using Mike's template for new targets). The patch also lists the instructions implemented by each section, so that it's possible to search the file by instruction mnemonic. I wouldn't be surprised if I end up having to rip out the contents section, but I found it useful for the month or so that that I've been using it locally. The patch checks that the contents remain up-to-date by running a checking script during an early stage of the build. No functional change intended. 2019-08-07 Richard Sandiford <richard.sandiford@arm.com> gcc/ * config/aarch64/aarch64-sve.md: Reorganize contents and add banner comments. * config/aarch64/check-sve-md.awk: New file. * config/aarch64/t-aarch64 (s-check-sve-md): New rule. (insn-conditions.md): Depend on it. From-SVN: r274184
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.