Go to file
Jan Beulich 9386188e95 x86-64: improve handling of branches to absolute addresses
There are two related problems here: The use of "addr32" on a direct
branch would, besides causing a warning, result in operands to be
permitted which mistakenly are refused without "addr32". Plus at some
point not too long ago I'm afraid it may have been me who regressed the
relocation addends emitted for such branches. Correct both problems,
adding a testcase to guard against regressing this again.
2022-07-04 08:31:21 +02:00
bfd RISC-V: Update Zihintpause extension version 2022-07-04 08:45:54 +08:00
binutils Add newline to the end of the rnglists displsy. 2022-07-01 15:08:44 +01:00
config
contrib
cpu drop XC16x bits 2022-06-27 11:11:46 +02:00
elfcpp
etc
gas x86-64: improve handling of branches to absolute addresses 2022-07-04 08:31:21 +02:00
gdb [gdb/symtab] Fix data race on per_cu->dwarf_version 2022-07-02 13:03:34 +02:00
gdbserver Fix GDBserver regression due to change to avoid reading shell registers 2022-06-29 19:32:07 +01:00
gdbsupport [gdb] Block SIGTERM in worker threads 2022-06-30 13:31:06 +02:00
gnulib
gold Have gold's File_read::do_read() function check the start parameter 2022-06-27 13:07:40 +01:00
gprof
gprofng gprofng: fix build when BUILD_MAN is false 2022-06-28 21:36:26 -07:00
include opcodes/aarch64: split off creation of comment text in disassembler 2022-06-29 12:03:22 +01:00
intl
ld Re: ld/x86: skip p_align-1 tests with unsuitable compiler 2022-06-29 10:15:55 +09:30
libbacktrace
libctf libctf: tests: prune warnings from compiler output 2022-06-21 19:27:15 +01:00
libdecnumber
libiberty
opcodes opcodes/aarch64: split off creation of comment text in disassembler 2022-06-29 12:03:22 +01:00
readline
sim sim: fix BFD_VMA format arguments on 32-bit hosts [PR gdb/29184] 2022-06-15 23:12:56 +01:00
texinfo
zlib
.cvsignore
.editorconfig
.gitattributes
.gitignore
ar-lib
ChangeLog
compile
config-ml.in
config.guess
config.rpath
config.sub
configure [gdb/build] Fix build breaker with --enable-shared 2022-06-27 15:36:19 +02:00
configure.ac [gdb/build] Fix build breaker with --enable-shared 2022-06-27 15:36:19 +02:00
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.