Go to file
Tom Tromey 2b7c3f1dc0 Split gdbarch.h into two files
This patch splits gdbarch.h into two files -- gdbarch.h now is
editable and hand-maintained, and the new gdbarch-gen.h file is the
only thing generated by gdbarch.sh.  This lets us avoid maintaining
boilerplate in the gdbarch.sh file.

Note that gdbarch.sh still generates gdbarch.h after this patch.  This
makes it easier to re-run when rebasing.  This code is removed in a
subsequent patch.
2021-12-17 14:53:44 -07:00
bfd asan: NULL dereference in bfd_elf_set_group_contents 2021-12-17 16:54:56 +10:30
binutils try_build_id_prefix gcc-10 -Wformat-security errors 2021-12-17 11:42:18 +10:30
config
contrib
cpu
elfcpp [GOLD] PowerPC64 @notoc in non-power10 code 2021-12-11 14:52:36 +10:30
etc
gas Fix AVR assembler so that it creates relocs that will work with linker relaxation. 2021-12-16 16:40:57 +00:00
gdb Split gdbarch.h into two files 2021-12-17 14:53:44 -07:00
gdbserver New --enable-threading configure option to control use of threads in GDB/GDBserver 2021-12-15 17:00:00 -03:00
gdbsupport New --enable-threading configure option to control use of threads in GDB/GDBserver 2021-12-15 17:00:00 -03:00
gnulib
gold [GOLD] PowerPC64 @notoc in non-power10 code 2021-12-11 14:52:36 +10:30
gprof gprof: enable silent build rules 2021-11-29 20:28:29 -05:00
include arm: Add support for Armv9.1-A to Armv9.3-A 2021-12-16 09:32:00 +00:00
intl
ld Fix AVR assembler so that it creates relocs that will work with linker relaxation. 2021-12-16 16:40:57 +00:00
libbacktrace
libctf libctf: workaround automake bug with conditional info pages 2021-12-02 23:26:18 -05:00
libdecnumber
libiberty
opcodes RISC-V: Support svinval extension with frozen version 1.0. 2021-12-16 16:04:53 +08:00
readline
sim sim: mips/or1k: drop redundant arg to bitsize macro 2021-12-16 02:36:10 -05:00
texinfo
zlib zlib: enable silent build rules 2021-11-29 20:28:29 -05:00
.cvsignore
.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.