Newlib modified for the FreeChainXenon project
Find a file
Marcus Shawcroft 0a4019eed2 [ARM] Select appropriate memcpy implementation for ARMv8-a.
The newlib configury logic that detects architecture version and
chooses an appropriate memcpy implementation does not consider
ARMv8-a.

This patch adds configury logic to detect ARMv8-a along with the
associated changes in Makefile.am and memcpy.
2015-11-03 11:04:55 +00:00
config 2014-05-14 Sandra Loosemore <sandra@codesourcery.com> 2014-05-14 23:24:37 +00:00
etc
include For the RX port, avoid using string instructions when __RX_DISALLOW_STRING_INSNS__ is defined. 2015-04-23 21:57:13 +02:00
libgloss * rl78/crt0.S (_start): Fixed code that clears .bss 2015-10-20 21:37:06 -04:00
newlib [ARM] Select appropriate memcpy implementation for ARMv8-a. 2015-11-03 11:04:55 +00:00
texinfo
winsup Define MAX_IPOPTLEN 2015-11-02 15:42:30 +01:00
.gitattributes Add .gitattributes 2015-03-09 20:53:11 +01:00
.gitignore Add *.swp (Vim swap files) to .gitignore 2015-03-17 12:03:30 +01:00
ChangeLog Consistently use an em-dash in math functions. 2015-11-02 16:43:22 -05:00
compile
config-ml.in
config.guess config.{guess,sub}: sync with upstream 2015-09-22 09:25:18 -04:00
config.rpath
config.sub config.{guess,sub}: sync with upstream 2015-09-22 09:25:18 -04:00
configure * configure.ac: Don't accept isl 0.10. 2014-07-05 21:09:07 +00:00
configure.ac * configure.ac: Don't accept isl 0.10. 2014-07-05 21:09:07 +00:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS Add FTDI license for newlib and libgloss. 2015-09-04 14:43:38 -04:00
COPYING.NEWLIB Add FTDI license for newlib and libgloss. 2015-09-04 14:43:38 -04:00
COPYING3
COPYING3.LIB
depcomp
djunpack.bat
install-sh
libtool.m4 * libtool.m4 (_LT_ENABLE_LOCK <ld -m flags>): Remove non-canonical 2013-09-20 09:51:24 +00:00
ltgcc.m4
ltmain.sh PR target/59788 2014-02-05 13:17:47 +00:00
ltoptions.m4
ltsugar.m4
ltversion.m4
lt~obsolete.m4
MAINTAINERS MAINTAINERS: clarify policy with config/ (and other top level files) 2012-05-12 03:10:17 +00:00
Makefile.def 2013-08-12 Jan-Benedict Glaw <jbglaw@lug-owl.de> 2013-08-12 11:36:35 +00:00
Makefile.in 2013-08-12 Jan-Benedict Glaw <jbglaw@lug-owl.de> 2013-08-12 11:36:35 +00:00
Makefile.tpl * Makefile.tpl (BOOT_ADAFLAGS): Remove -gnata. 2013-01-11 11:48:54 +00:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release * src-release (do-proto-toplevel): Support subdir-path-prefixed 2013-10-15 20:45:52 +00: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.