Binutils with MCST patches
Go to file
Alan Modra 7455c018e4 PR23207, hppa ld SIGSEGVs on invalid object files
We don't create PLT call stubs for anything in non-alloc sections,
so it doesn't pay to go looking for them.  The problem is that
non-alloc sections aren't processed by group_sections and thus don't
get a link_sec set up for them.

	PR 23207
	* elf32-hppa.c (final_link_relocate): Don't look for plt call
	stubs in non-alloc sections.
2018-05-22 14:45:15 +09:30
bfd PR23207, hppa ld SIGSEGVs on invalid object files 2018-05-22 14:45:15 +09:30
binutils RISC-V: Add RV32E support. 2018-05-18 14:03:18 -07:00
config config: Sync with GCC 2018-04-05 15:22:13 -07:00
cpu PR22069, Several instances of register accidentally spelled as regsiter 2018-05-09 15:55:28 +09:30
elfcpp PowerPC inline PLT call support 2018-04-09 17:25:20 +09:30
etc
gas Remove fake operand handling for extended mnemonics. 2018-05-21 17:31:07 -05:00
gdb MIPS/Linux: Disable n32 USR `ptrace' accesses to 64-bit registers 2018-05-22 01:52:35 +01:00
gold Fix _GLOBAL_OFFSET_TABLE_ value for large GOTs (aarch64). 2018-05-10 00:13:33 -07:00
gprof Updated Spanish translation for gprof directory 2018-04-18 12:02:17 +01:00
include Remove fake operand handling for extended mnemonics. 2018-05-21 17:31:07 -05:00
intl
ld ld: Adjust tic6x tests 2018-05-21 20:41:24 -07:00
libdecnumber
libiberty Resync libiberty sources with master version in GCC repository. 2018-04-17 13:53:38 +01:00
opcodes Remove fake operand handling for extended mnemonics. 2018-05-21 17:31:07 -05:00
readline
sim PR22069, Several instances of register accidentally spelled as regsiter 2018-05-09 15:55:28 +09:30
texinfo
zlib
.cvsignore
.gitattributes
.gitignore
ChangeLog Bring in support for the NFP target in the config.sub file. 2018-05-01 16:35:04 +01:00
compile
config-ml.in
config.guess Bring in support for the NFP target in the config.sub file. 2018-05-01 16:35:04 +01:00
config.rpath
config.sub Bring in support for the NFP target in the config.sub file. 2018-05-01 16:35:04 +01:00
configure Add the Netronome Flow Processor as a build target to the top-level configure.ac file. 2018-05-01 16:23:21 +01:00
configure.ac Add the Netronome Flow Processor as a build target to the top-level configure.ac file. 2018-05-01 16:23:21 +01: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
README
README-maintainer-mode
setup.com
src-release.sh
symlink-tree
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.