Binutils with MCST patches
Go to file
Maciej W. Rozycki 55af478400 MIPS16/opcodes: Reformat raw EXTEND and undecoded output
Use a tab rather than a space to separate `extend' and its uninterpreted
argument output, like with regular instructions.  Separate hexadecimal
halves of undecoded extended instructions output with a space instead of
presenting them concatenated.

	opcodes/
	* mips-dis.c (print_insn_mips16): Use a tab rather than a space
	to separate `extend' and its uninterpreted argument output.
	Separate hexadecimal halves of undecoded extended instructions
	output.

	binutils/
	* testsuite/binutils-all/mips/mips16-extend-noinsn.d: New test.
	* testsuite/binutils-all/mips/mips16-extend-noinsn.s: New test
	source.
	* testsuite/binutils-all/mips/mips.exp: Run the new test.
2016-12-09 23:18:06 +00:00
bfd Automatic date update in version.in 2016-12-09 00:00:25 +00:00
binutils MIPS16/opcodes: Reformat raw EXTEND and undecoded output 2016-12-09 23:18:06 +00:00
config sync binutils config/ with gcc 2016-12-08 21:35:11 +10:30
cpu
elfcpp
etc
gas ARC/GAS: Correct a `spaces' global shadowing error 2016-12-08 23:24:05 +00:00
gdb gdb: Remove support for obsolete OSABIs and a.out 2016-12-09 16:08:49 +00:00
gold [GOLD] Don't assert in powerpc stub_table 2016-12-08 22:18:47 +10:30
gprof Fix spelling in comments in C source files (gprof) 2016-11-27 15:04:01 +10:30
include MIPS/include: opcode/mips.h: Correct INSN_CHIP_MASK 2016-12-07 12:31:38 +00:00
intl
ld sync binutils config/ with gcc 2016-12-08 21:35:11 +10:30
libdecnumber
libiberty sync binutils config/ with gcc 2016-12-08 21:35:11 +10:30
opcodes MIPS16/opcodes: Reformat raw EXTEND and undecoded output 2016-12-09 23:18:06 +00:00
readline
sim Fix bugs with tbnz/tbz instructions. 2016-12-03 17:29:44 -08:00
texinfo
zlib sync binutils config/ with gcc 2016-12-08 21:35:11 +10:30
.cvsignore
.gitattributes
.gitignore
ChangeLog sync binutils config/ with gcc 2016-12-08 21:35:11 +10:30
compile
config-ml.in
config.guess
config.rpath
config.sub
configure sync binutils config/ with gcc 2016-12-08 21:35:11 +10:30
configure.ac Add support for Fushia OS. 2016-12-02 10:44:29 +00: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
Makefile.in
Makefile.tpl
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release.sh
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.