Go to file
Richard Sandiford f5b57feac2 aarch64: Add support for strided register lists
SME2 has instructions that accept strided register lists,
such as { z0.s, z4.s, z8.s, z12.s }.  The purpose of this
patch is to extend binutils to support such lists.

The parsing code already had (unused) support for strides of 2.
The idea here is instead to accept all strides during parsing
and reject invalid strides during constraint checking.

The SME2 instructions that accept strided operands also have
non-strided forms.  The errors about invalid strides therefore
take a bitmask of acceptable strides, which allows multiple
possibilities to be summed up in a single message.

I've tried to update all code that handles register lists.
2023-03-30 11:09:10 +01:00
bfd Fix an illegal memory access when an accessing a zer0-lengthverdef table. 2023-03-30 10:10:09 +01:00
binutils Fix an illegal memory access triggered by parsing corrupt DWARF info. 2023-03-30 11:04:53 +01:00
config
contrib
cpu
elfcpp
etc
gas aarch64: Add support for strided register lists 2023-03-30 11:09:10 +01:00
gdb gdb/python: Add new gdb.unwinder.FrameId class 2023-03-30 10:25:46 +01:00
gdbserver
gdbsupport gdb: move displaced_step_dump_bytes into gdbsupport (and rename) 2023-03-29 08:57:10 +01:00
gnulib
gold Add an option to the gold linker to put its version string into the .comment section. 2023-03-27 11:10:10 +01:00
gprof
gprofng gprofng: Add version symbols to libgprofng.ver 2023-03-29 23:09:40 -07:00
include aarch64: Add support for strided register lists 2023-03-30 11:09:10 +01:00
intl
ld Fix typo in ld manual --enable-non-contiguous-regions example 2023-03-29 17:05:32 -07:00
libbacktrace
libctf libctf: get the offsets of fields of unnamed structs/unions right 2023-03-24 13:37:32 +00:00
libdecnumber
libiberty
libsframe Remove unnecessary memsets in sframe-dump.c 2023-03-22 09:39:41 +10:30
opcodes aarch64: Add support for strided register lists 2023-03-30 11:09:10 +01:00
readline
sim
texinfo
zlib
.cvsignore
.editorconfig
.gitattributes
.gitignore
ar-lib
ChangeLog
compile
config-ml.in
config.guess
config.rpath
config.sub
configure
configure.ac
COPYING
COPYING3
COPYING3.LIB
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
depcomp
djunpack.bat
install-sh
libtool.m4
lt~obsolete.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
MAINTAINERS
Makefile.def
Makefile.in
Makefile.tpl
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
multilib.am
README
README-maintainer-mode
setup.com
src-release.sh
symlink-tree
test-driver
ylwrap

		   README for GNU development tools

This directory contains various GNU compilers, assemblers, linkers, 
debuggers, etc., plus their support routines, definitions, and documentation.

If you are receiving this as part of a GDB release, see the file gdb/README.
If with a binutils release, see binutils/README;  if with a libg++ release,
see libg++/README, etc.  That'll give you info about this
package -- supported targets, how to use it, how to report bugs, etc.

It is now possible to automatically configure and build a variety of
tools with one command.  To build all of the tools contained herein,
run the ``configure'' script here, e.g.:

	./configure 
	make

To install them (by default in /usr/local/bin, /usr/local/lib, etc),
then do:
	make install

(If the configure script can't determine your type of computer, give it
the name as an argument, for instance ``./configure sun4''.  You can
use the script ``config.sub'' to test whether a name is recognized; if
it is, config.sub translates it to a triplet specifying CPU, vendor,
and OS.)

If you have more than one compiler on your system, it is often best to
explicitly set CC in the environment before running configure, and to
also set CC when running make.  For example (assuming sh/bash/ksh):

	CC=gcc ./configure
	make

A similar example using csh:

	setenv CC gcc
	./configure
	make

Much of the code and documentation enclosed is copyright by
the Free Software Foundation, Inc.  See the file COPYING or
COPYING.LIB in the various directories, for a description of the
GNU General Public License terms under which you can copy the files.

REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info
on where and how to report problems.