Binutils with MCST patches
Go to file
Mike Frysinger 191ec03314 sim: microblaze: start a testsuite
Since the sim doesn't have any debug support in it, we can only exit
cleanly.  But this is still better than nothing.

Change the default microblaze sim to not dump the debug load output
when running.  No other does this, and it breaks the testsuite.
2015-03-29 16:45:49 -04:00
bfd Fix a typo in bfd/ChangeLog 2015-03-29 07:36:27 -07:00
binutils [Patch ]Fix bintest.s failure after previous AArch64 map symbol commit 2015-03-27 10:22:46 +00:00
config Sync isl.m4 with GCC tree 2015-03-16 08:51:37 -07:00
cpu
elfcpp [gold] Recognize DWARF5/GCC5 DW_LANG_Fortran03 and DW_LANG_Fortran08. 2015-02-17 08:08:24 +01:00
etc
gas Remove the unused cpu_flags_set 2015-03-27 09:29:05 -07:00
gdb gdb: ft32: new port 2015-03-28 02:13:34 -04:00
gold Avoid looking up Input_merge_map multiple times. 2015-03-27 09:51:15 -04:00
gprof
include sim: ft32: new port 2015-03-28 02:12:33 -04:00
intl
ld Don't run ld-x86-64/pr18160.d for x86_64-*-nacl* 2015-03-27 14:40:43 -07:00
libdecnumber
libiberty
opcodes Add the missing opcodes/ChangeLog entry 2015-03-29 07:46:30 -07:00
readline
sim sim: microblaze: start a testsuite 2015-03-29 16:45:49 -04:00
texinfo
zlib Import zlib from GCC 2015-03-26 08:25:29 -07:00
.cvsignore
.gitattributes
.gitignore
ChangeLog A zlib to tarball 2015-03-28 06:48:43 -07:00
compile
config-ml.in Sync config-ml.in with GCC trunk 2015-03-17 05:15:34 -07:00
config.guess
config.rpath
config.sub
configure Exclude target-zlib if target-libjava isn't built 2015-03-17 17:07:22 -07:00
configure.ac Exclude target-zlib if target-libjava isn't built 2015-03-17 17:07:22 -07: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 Update top-level files from GCC trunk 2015-03-16 09:12:37 -07:00
Makefile.in Update top-level files from GCC trunk 2015-03-16 09:12:37 -07:00
Makefile.tpl Update top-level files from GCC trunk 2015-03-16 09:12:37 -07:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release.sh A zlib to tarball 2015-03-28 06:48:43 -07:00
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.