Go to file
Jakub Jelinek 19f7b01094 gas/
* config/tc-sparc.c (sparc_ip): Fix a bug which caused v9_arg_p
	instructions to loose any special insn->architecture mask.

	* config/tc-sparc.c (v9a_asr_table): Add v9b ASRs.
	(sparc_md_end, sparc_arch_types, sparc_arch,
	sparc_elf_final_processing): Handle v8plusb and v9b architectures.
	(sparc_ip): Handle siam mode operands. Support v9b ASRs (and
	request v9b architecture if they are used).

bfd/
	* elf32-sparc.c (elf32_sparc_merge_private_bfd_data,
	elf32_sparc_object_p, elf32_sparc_final_write_processing):
	Support v8plusb.
	* elf64-sparc.c (sparc64_elf_merge_private_bfd_data,
	sparc64_elf_object_p): Support v9b.
	* archures.c: Declare v8plusb and v9b machines.
	* bfd-in2.h: Ditto.
	* cpu-sparc.c: Ditto.

include/opcode/
	* sparc.h (enum sparc_opcode_arch_val): Add SPARC_OPCODE_ARCH_V9B.
	Note that '3' is used for siam operand.

opcodes/
	* sparc-dis.c (v9a_asr_reg_names): Add v9b ASRs.
	(compute_arch_mask): Add v8plusb and v9b machines.
	(print_insn_sparc): siam mode decoding, accept ASRs up to 25.
	* opcodes/sparc-opc.c: Support for Cheetah instruction set.
	(prefetch_table): Add #invalidate.
2000-10-20 10:38:47 +00:00
bfd gas/ 2000-10-20 10:38:47 +00:00
binutils (readelf -S test, readelf -s test): Expect mips*-*-* to fail. 2000-10-19 18:04:56 +00:00
config
etc
gas gas/ 2000-10-20 10:38:47 +00:00
gdb Add Fred Fish to the Blanket Write Privs list. 2000-10-20 08:21:45 +00:00
gprof * ltconfig, ltmain.sh, libtool.m4: Updated from libtool 2000-09-30 06:07:00 +00:00
include gas/ 2000-10-20 10:38:47 +00:00
intl
ld 2000-10-19 H.J. Lu (hjl@gnu.org) 2000-10-19 19:52:28 +00:00
libiberty merge from gcc repository 2000-10-12 02:16:48 +00:00
mmalloc
opcodes gas/ 2000-10-20 10:38:47 +00:00
readline
sim * cleanup 2000-10-19 10:52:52 +00:00
texinfo
.cvsignore
ChangeLog * ltconfig, ltmain.sh, libtool.m4: Updated from libtool 2000-09-30 06:07:00 +00:00
config-ml.in
config.guess
config.if
config.sub
configure
configure.in
COPYING
COPYING.LIB
djunpack.bat
gettext.m4
install-sh
libtool.m4 * ltconfig, ltmain.sh, libtool.m4: Updated from libtool 2000-09-30 06:07:00 +00:00
ltcf-c.sh
ltconfig * ltconfig, ltmain.sh, libtool.m4: Updated from libtool 2000-09-30 06:07:00 +00:00
ltmain.sh * ltconfig, ltmain.sh, libtool.m4: Updated from libtool 2000-09-30 06:07:00 +00:00
MAINTAINERS
Makefile.in
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
mpw-build.in
mpw-config.in
mpw-configure
mpw-install
mpw-README
README
README-maintainer-mode
setup.com
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.