Go to file
Jan Beulich ae89daecb1 x86: generalize disabling of sub-architectures
I never really understood upon what basis ".arch .no*" options were made
available. Let's not have any "criteria" at all, and simply allow
disabling of all of them. Then we also have all data for a sub-arch in
a single place, as we now only need a single table.
2022-07-06 09:22:11 +02:00
bfd Automatic date update in version.in 2022-07-06 00:00:17 +00:00
binutils Support for location and range lists for split-dwarf and dwarf-5. 2022-07-05 16:56:13 +05:30
config
contrib
cpu drop XC16x bits 2022-06-27 11:11:46 +02:00
elfcpp
etc
gas x86: generalize disabling of sub-architectures 2022-07-06 09:22:11 +02:00
gdb [gdb/exp] Fix internal error when printing C++ pointer-to-member 2022-07-05 22:41:25 +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 Fix snafu in rust demangler recursion limit code 2022-07-04 16:28:02 +01:00
opcodes opcodes/avr: Implement style support in the disassembler 2022-07-04 11:25:42 +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 Synchronize libbierty sources with gcc. 2022-07-04 13:57:12 +01:00
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.