Go to file
Alan Modra 856c1545ce bfd_reloc_offset_in_range overflow
This patch is more about the style of bounds checking we ought to use,
rather than a real problem.  An overflow of "octet + reloc_size" can
only happen with huge sections which would certainly cause out of
memory errors.

	* reloc.c (bfd_reloc_offset_in_range): Avoid possible overflow.
2021-08-06 23:06:53 +09:30
bfd bfd_reloc_offset_in_range overflow 2021-08-06 23:06:53 +09:30
binutils PR28156, rename.c doesn't compile with MinGW 2021-08-04 14:44:08 +09:30
config Add markers for 2.37 branch 2021-07-03 14:50:57 +01:00
contrib
cpu Re: opcodes: constify & local meps macros 2021-07-05 21:40:49 +09:30
elfcpp Add markers for 2.37 branch 2021-07-03 14:50:57 +01:00
etc texi2pod.pl: add no-op --no-split option support [PR28144] 2021-07-28 11:39:40 +01:00
gas [PATCH 2/2] Add tests for Intel AVX512_FP16 instructions 2021-08-05 21:03:41 +08:00
gdb [PATCH] GDB Testsuite, update compile-cplus.exp 2021-08-05 13:04:35 -05:00
gdbserver Fix the Windows build 2021-07-26 07:34:37 -06:00
gdbsupport gdbsupport: add debug assertions in gdb::optional::get 2021-08-03 08:50:56 -04:00
gnulib
gold PR28106, build of 2.37 fails on FreeBSD and Clang 2021-07-20 20:15:48 +09:30
gprof Updated translations (mainly Ukranian and French) triggered by creation of 2.37 branch. 2021-07-05 15:54:35 +01:00
include PATCH [6/10] arm: Add -march=armv8.1-m.main+pacbti flag 2021-07-26 14:18:24 +02:00
intl
ld Re: elf: Treat undefined version as hidden 2021-08-05 20:47:09 +09:30
libctf Add markers for 2.37 branch 2021-07-03 14:50:57 +01:00
libdecnumber
libiberty Restore the libiberty component of commit 50ad1254d5. 2021-07-05 16:21:42 +01:00
opcodes [PATCH 1/2] Enable Intel AVX512_FP16 instructions 2021-08-05 21:03:41 +08:00
readline
sim sim: erc32: use libsim.a for common objects 2021-07-08 02:30:37 -04:00
texinfo
zlib
.cvsignore
.gitattributes
.gitignore
ar-lib
ChangeLog Add markers for 2.37 branch 2021-07-03 14:50:57 +01:00
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.