Go to file
Jan Beulich fb40ea39de x86: simplify / consolidate check_{word,long,qword}_reg()
These run after template matching. Therefore operands are already known
to match the template in use. With the loop bodies skipping anything not
a GPR in the actual operands, there's therefore no need to check the
template's operand type for permitting Reg or Accum.

At the same time bring the three functions in sync for the "byte" part
of the logic, as far as checking the template for other sizes (qword
specifically) goes. Plus drop a stale comment from check_qword_reg(),
when all three are now behaving the same in this regard.
2024-05-24 11:51:21 +02:00
bfd Automatic date update in version.in 2024-05-24 00:00:23 +00:00
binutils readelf: add pretty printing for FDO Dlopen Metadata note 2024-05-20 16:47:00 +01:00
config
contrib
cpu
elfcpp
etc
gas x86: simplify / consolidate check_{word,long,qword}_reg() 2024-05-24 11:51:21 +02:00
gdb [gdb/testsuite] Add PR26286 kfail in gdb.threads/attach-many-short-lived-threads.exp 2024-05-24 09:36:52 +02:00
gdbserver Stop 'configure --enable-threading' if std::thread doesn't work 2024-05-16 13:03:58 +01:00
gdbsupport Stop 'configure --enable-threading' if std::thread doesn't work 2024-05-16 13:03:58 +01:00
gnulib
gold
gprof
gprofng gprofng: use StringBuilder to create long messages 2024-05-21 19:54:59 -07:00
include include, libctf: improve documentation 2024-05-21 11:15:19 +01:00
ld ld: silence makeinfo warnings 2024-05-21 13:42:25 +02:00
libbacktrace
libctf libctf testsuite compilation failure 2024-05-23 08:11:12 +09:30
libdecnumber
libiberty
libsframe
opcodes x86: correct VCVT{,U}SI2SD 2024-05-24 11:50:38 +02:00
readline
sim sim: riscv: Fix build issue due to recent binutils commit 2024-05-09 17:04:14 +02:00
texinfo
zlib
.cvsignore
.editorconfig
.gitattributes
.gitignore
.pre-commit-config.yaml gdb: bump black version to 24.4.2 2024-05-16 11:34:40 -04:00
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
SECURITY.txt
setup.com
src-release.sh Add extra files found in etc/ sub-directory to ETC_SUPPORT in src-release.sh 2024-05-20 16:12:53 +01:00
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.