Binutils with MCST patches
Go to file
Jakub Jelinek 4fd61dcb07 * i386-dis.c (grps): Use INVLPG_Fixup instead of OP_E for invlpg.
(INVLPG_Fixup): New function.
	(PNI_Fixup): Remove ATTRIBUTE_UNUSED from sizeflag.

	* opcode/i386.h (i386_optab): Remove CpuNo64 from sysenter and
	sysexit.
2004-03-12 10:47:49 +00:00
bfd daily update 2004-03-11 23:00:05 +00:00
binutils * MAINTAINERS: Update my mail address. 2004-03-10 02:58:24 +00:00
config (top level) 2004-03-11 05:15:36 +00:00
contrib
cpu Add fr450 support. 2004-03-01 10:11:46 +00:00
etc
gas 2004-03-12 Michal Ludvig <mludvig@suse.cz> 2004-03-12 10:14:29 +00:00
gdb *** empty log message *** 2004-03-12 00:00:03 +00:00
gprof
include * i386-dis.c (grps): Use INVLPG_Fixup instead of OP_E for invlpg. 2004-03-12 10:47:49 +00:00
intl
ld Honour PRIVATE keyword 2004-03-08 11:33:59 +00:00
libiberty merge from gcc 2004-03-10 01:02:12 +00:00
mmalloc
opcodes * i386-dis.c (grps): Use INVLPG_Fixup instead of OP_E for invlpg. 2004-03-12 10:47:49 +00:00
readline Index: ChangeLog 2004-02-19 14:55:26 +00:00
sim * MAINTAINERS: Update my mail address. 2004-03-10 02:58:24 +00:00
texinfo 2004-02-23 Andrew Cagney <cagney@redhat.com> 2004-02-23 19:37:48 +00:00
.cvsignore
ChangeLog 2004-03-11 Eric Botcazou <ebotcazou@gcc.gnu.org> 2004-03-11 18:30:52 +00:00
config-ml.in
config.guess Index: ChangeLog 2004-02-19 14:55:26 +00:00
config.if
config.sub Index: ChangeLog 2004-02-19 14:55:26 +00:00
configure 2004-03-11 Eric Botcazou <ebotcazou@gcc.gnu.org> 2004-03-11 18:30:52 +00:00
configure.in 2004-03-11 Eric Botcazou <ebotcazou@gcc.gnu.org> 2004-03-11 18:30:52 +00:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB 2004-02-02 Jeff Johnston <jjohnstn@redhat.com> 2004-02-03 00:05:49 +00:00
djunpack.bat
gettext.m4 * gettext.m4: Quote names of macros to be defined by AC_DEFUN 2004-01-14 13:41:37 +00:00
install-sh PR bootstrap/11932 2004-02-20 02:05:00 +00:00
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh
MAINTAINERS
Makefile.def 2004-02-10 Arnaud Charlet <charlet@act-europe.fr>, 2004-02-10 17:57:02 +00:00
Makefile.in PR bootstrap/7087 2004-02-28 22:03:47 +00:00
Makefile.tpl PR bootstrap/7087 2004-02-28 22:03:47 +00:00
makefile.vms
missing
mkdep
mkinstalldirs PR bootstrap/11932 2004-02-20 02:05:00 +00:00
move-if-change
mpw-build.in
mpw-config.in
mpw-configure
mpw-install
mpw-README
README
README-maintainer-mode
setup.com
src-release 2004-02-28 Andrew Cagney <cagney@redhat.com> 2004-02-28 21:52:04 +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.