Go to file
Cl?ment Chigot bdd2aaf69e fix string table generation for XCOFF64 .debug section
bfd	* hash.c (struct bfd_strtab_hash): Remove xcoff field.
	Add length_field_size field.
	(_bfd_stringtab_init): Change prototype.
	Adapt to new length_field_size.
	(_bfd_xcoff_stringtab_init): Likewise.
	(_bfd_stringtab_add): Likewise.
	(_bfd_stringtab_emit): Likewise.
	* libbfd-in.h (_bfd_xcoff_stringtab_init):
	Change prototype.
	* libbfd.h: Regenerate.
	* xcofflink.c (_bfd_xcoff_bfd_link_hash_table_create):
	Call _bfd_xcoff_stringtab_init with isxcoff64 value.
2021-04-22 15:31:02 +01:00
bfd fix string table generation for XCOFF64 .debug section 2021-04-22 15:31:02 +01:00
binutils Harmonize and improve auxiliary entries support for XCOFF 2021-04-22 12:28:50 +01:00
config
contrib
cpu Use bool in opcodes 2021-03-31 10:49:23 +10:30
elfcpp
etc
gas Adjust readelf's output so that section symbols without a name as shown with their section name. 2021-04-21 10:34:32 +01:00
gdb Improve code coverage of Rust testing 2021-04-22 07:16:36 -06:00
gdbserver Remove use of _WIN32_WCE 2021-04-14 06:45:44 -06:00
gdbsupport New memory-tag commands 2021-03-24 14:57:53 -03:00
gnulib gnulib: import gitlog-to-changelog 2021-03-24 19:35:40 -04:00
gold PR27625, powerpc64 gold __tls_get_addr calls 2021-03-30 13:38:41 +10:30
gprof PR27716, build failure for msdosdjgpp: PATH_MAX undeclared 2021-04-14 15:06:11 +09:30
include Harmonize and improve auxiliary entries support for XCOFF 2021-04-22 12:28:50 +01:00
intl
ld x86-64/PE: adjust PR ld/26659 testcase for Cygwin 2021-04-22 10:55:07 +02:00
libctf libctf: fix ELF-in-BFD checks in the presence of ASAN 2021-03-25 16:32:51 +00:00
libdecnumber
libiberty
opcodes aarch64: New instructions for maintenance of GPT entries cached in a TLB 2021-04-19 15:01:56 +01:00
readline
sim sim: regen against sim/m4/ 2021-04-21 20:40:51 -04:00
texinfo
zlib
.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.