No description
Find a file
David S. Miller 698544e152 Add support for sparc compare-and-branch instructions.
opcodes/

	* sparc-opc.c (CBCOND): New define.
	(CBCOND_XCC): Likewise.
	(cbcond): New helper macro.
	(sparc_opcodes): Add compare-and-branch instructions.

gas/

	* config/tc-sparc.c (sparc_arch_table): Add HWCAP_CBCOND to
	sparc4, v8pluse, v8plusv, v9e, and v9v.
	(sparc_ip): Handle R_SPARC_5 of immediate constants inline in
	order to accomodate cbcond which otherwise would require two
	relocations to be handled in a single instruction..

gas/testsuite/

	* gas/sparc/cbcond.s: New file.
	* gas/sparc/cbcond.d: New file.
	* gas/sparc/sparc.exp: Run cbcond test.
2012-04-27 18:03:13 +00:00
bfd daily update 2012-04-27 00:00:05 +00:00
binutils * doc/binutils.texi: Add -D/--enable-deterministic-archives option 2012-04-25 17:50:14 +00:00
config
cpu
elfcpp elfcpp/ 2012-04-23 23:31:15 +00:00
etc
gas Add support for sparc compare-and-branch instructions. 2012-04-27 18:03:13 +00:00
gdb *** empty log message *** 2012-04-27 00:00:33 +00:00
gold * arm.cc (Target_arm::do_is_defined_by_abi): Make sym a const 2012-04-26 00:07:21 +00:00
gprof 2012-03-06 Tristan Gingold <gingold@adacore.com> 2012-03-06 13:54:59 +00:00
include Add support for SPARC T4 crypto instructions. 2012-04-27 18:02:35 +00:00
intl
ld Make bfd asserts cause linker errors. 2012-04-26 13:51:14 +00:00
libdecnumber
libiberty merge from gcc 2012-04-10 17:07:35 +00:00
opcodes Add support for sparc compare-and-branch instructions. 2012-04-27 18:03:13 +00:00
readline
sim sim: bfin: new PINT model 2012-04-09 06:13:06 +00:00
texinfo
.cvsignore
.gitignore
ChangeLog Update config.sub to 2012-04-18 version. 2012-04-25 15:53:25 +00:00
compile
config-ml.in
config.guess
config.rpath
config.sub Update config.sub to 2012-04-18 version. 2012-04-25 15:53:25 +00:00
configure * configure.ac (ia64*-*-*vms*): Add support for ld. 2012-04-12 07:35:07 +00:00
configure.ac * configure.ac (ia64*-*-*vms*): Add support for ld. 2012-04-12 07:35:07 +00:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS 2012-03-09 Jeff Johnston <jjohnstn@redhat.com> 2012-03-09 20:31:34 +00:00
COPYING.NEWLIB 2012-03-09 Jeff Johnston <jjohnstn@redhat.com> 2012-03-09 20:31:34 +00:00
COPYING3
COPYING3.LIB
depcomp
djunpack.bat
install-sh
libtool.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
lt~obsolete.m4
MAINTAINERS
Makefile.def
Makefile.in
Makefile.tpl
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release
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.