Binutils with MCST patches
Go to file
Evandro Menezes 2412d87834 [AArch64] Add support for the Samsung Exynos M1 processor
2015-03-26  Evandro Menezes  <e.menezes@samsung.com>

gas/
	* config/tc-aarch64.c: Add support for Samsung Exynos M1.
	* doc/c-aarch64.texi (-mcpu=): Add "exynos-m1".
2015-04-01 21:00:41 +00:00
bfd [AArch64] Workaround for Cortex A53 erratum 843419 2015-04-01 13:16:38 +01:00
binutils Regenerate configure in bfd/binutils/gas/gdb 2015-04-01 04:55:48 -07:00
config Unset zlibdir/zlibinc only for --with-system-zlib 2015-04-01 04:51:55 -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 [AArch64] Add support for the Samsung Exynos M1 processor 2015-04-01 21:00:41 +00:00
gdb Add support for writing unwinders in Python. 2015-04-01 11:49:12 -07:00
gold Convert mov foo@GOT(%reg), %reg to lea foo@GOTOFF(%reg), %reg 2015-04-01 16:52:09 +03:00
gprof
include sim: ft32: new port 2015-03-28 02:12:33 -04:00
intl
ld Work around a GCC uninitialized warning bug 2015-04-01 08:14:32 -07:00
libdecnumber
libiberty
opcodes opcodes: d10v: fix old style prototype 2015-03-30 02:20:22 -04:00
readline
sim Fix sim build 2015-04-01 10:27:43 -07:00
texinfo
zlib Add missing ChangeLog entry 2015-03-31 13:15:01 -07:00
.cvsignore
.gitattributes
.gitignore
ChangeLog Add --with-system-zlib to top level configure 2015-04-01 04:57:28 -07:00
compile
config-ml.in Sync config-ml.in with GCC trunk 2015-03-17 05:15:34 -07:00
config.guess Update config.guess and config.sub to the latest upstream version 2015-03-30 16:28:14 -04:00
config.rpath
config.sub Update config.guess and config.sub to the latest upstream version 2015-03-30 16:28:14 -04:00
configure Add --with-system-zlib to top level configure 2015-04-01 04:57:28 -07:00
configure.ac Add --with-system-zlib to top level configure 2015-04-01 04:57:28 -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 Make all-bfd depend on all-zlib 2015-03-30 10:18:34 -07:00
Makefile.in Make all-bfd depend on all-zlib 2015-03-30 10:18:34 -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 Remove --with-target-subdir=. --disable-multilib 2015-03-31 13:13:13 -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.