freebsd-skq/contrib/binutils
Justin Hibbits e0b603cb9e Add rfdi opcode to binutils
The rfdi instruction is part of the e500mc and derivative cores.  It came into
binutils in a GPLv3 patch, along with the rest of the e500mc instruction set.
Currently only rfdi is planned to be used, so rather than attempt to backport
the full patch, take a surgical route and add instructions as needed.

MFC after:	2 weeks
2017-02-01 02:42:45 +00:00
..
bfd libbfd: make sure variables are initialized before using them. 2016-12-16 00:35:59 +00:00
binutils Generate manpage out of the texinfo files using texi2mdoc 2015-03-02 17:20:34 +00:00
config Clean some 'svn:executable' properties in the tree. 2013-01-26 22:08:21 +00:00
etc
gas add octeon+ as an alias for octeon in GCC & binutils 2017-01-27 21:31:32 +00:00
gprof
include Replace local prototype of basename() with an inclusion of <libgen.h>. 2016-05-29 16:10:01 +00:00
ld Remove pregenerated text version of the texinfo documentation 2015-03-02 17:25:03 +00:00
libiberty Clean up hardcoded ar(1) flags in the tree to use the global ARFLAGS in 2012-12-06 01:31:25 +00:00
opcodes Add rfdi opcode to binutils 2017-02-01 02:42:45 +00:00
ChangeLog
config-ml.in
config.guess
config.rpath
config.sub
configure
configure.ac
FREEBSD-deletelist
FREEBSD-upgrade
FREEBSD-Xlist
install-sh
libtool.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
MAINTAINERS
Makefile.def
Makefile.in Clean up hardcoded ar(1) flags in the tree to use the global ARFLAGS in 2012-12-06 01:31:25 +00:00
Makefile.tpl Clean up hardcoded ar(1) flags in the tree to use the global ARFLAGS in 2012-12-06 01:31:25 +00:00
missing
mkinstalldirs
move-if-change
README
README-maintainer-mode
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.