Binutils with MCST patches
Go to file
Mark Wielaard ddc5804ebd libiberty: demangler crash with missing :? or fold expression component.
When constructing an :? or fold expression that requires a third
expression only the first and second were explicitly checked to
not be NULL. Since the third expression is also required in these
constructs it needs to be explicitly checked and rejected when missing.
Otherwise the demangler will crash once it tries to d_print the
NULL component. Added two examples to demangle-expected of strings
that would crash before this fix.

Found by American Fuzzy Lop (afl) fuzzer.
2016-11-18 11:06:18 +01:00
bfd Help diagnose problems with the metag target when mixing static and shared binaries. 2016-11-18 09:27:41 +00:00
binutils Generate correct hint value for IDATA6. 2016-11-14 16:30:45 +00:00
config
cpu Add fall through comment to source in cpu/ 2016-10-06 22:48:37 +10:30
elfcpp
etc
gas [AArch64] Add ARMv8.3 FCMLA and FCADD instructions 2016-11-18 10:02:16 +00:00
gdb Makefile: Replace explicit subdir rules with pattern rules 2016-11-17 12:02:32 -05:00
gold Add missing '$' in configure.ac. 2016-11-07 08:00:21 -08:00
gprof Remove redundant assignment in gprof. 2016-10-06 12:51:47 +01:00
include Implement P0012R1, Make exception specifications part of the type system. 2016-11-18 11:06:18 +01:00
intl
ld Fix PR20789 - relaxation with negative valued diff relocs 2016-11-16 16:11:46 +05:30
libdecnumber
libiberty libiberty: demangler crash with missing :? or fold expression component. 2016-11-18 11:06:18 +01:00
opcodes [AArch64] Add ARMv8.3 FCMLA and FCADD instructions 2016-11-18 10:02:16 +00:00
readline
sim sim: mips: add PR info to ChangeLog 2016-11-12 01:02:23 -05:00
texinfo
zlib
.cvsignore
.gitattributes
.gitignore
ChangeLog Sync config.sub,config.guess with upstream. 2016-11-07 13:08:55 -08:00
compile
config-ml.in
config.guess Sync config.sub,config.guess with upstream. 2016-11-07 13:08:55 -08:00
config.rpath
config.sub Sync config.sub,config.guess with upstream. 2016-11-07 13:08:55 -08:00
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
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.