Binutils with MCST patches
Go to file
Ulrich Weigand 69368a60a4 * eval.c (evaluate_subexp_standard) [OP_OBJC_MSGCALL]: Support
platforms that use function descriptors.  Prefer to use function
	pointer types instead of function types.
	* linespec.c (decode_objc): Support function descriptors.  Fully
	initialize SAL result.
	* objc-lang.c (find_methods): Support function descriptors.
	Do not require function symbol to point to text section.

	* ppc-sysv-tdep.c (ppc64_sysv_abi_push_dummy_call): When calling
	via a function pointer, use the descriptor it points to.
2009-09-29 00:48:32 +00:00
bfd daily update 2009-09-29 00:00:05 +00:00
binutils * configure.in: Don't invoke configure.tgt on $enable_targets. 2009-09-28 12:48:16 +00:00
config config: 2009-09-09 19:46:42 +00:00
cpu * m32r.cpu (stb-plus): Typo fix. 2009-09-25 14:07:07 +00:00
elfcpp
etc
gas Update soruces to make alpha, arc and arm targets compile cleanly 2009-09-25 19:13:27 +00:00
gdb * eval.c (evaluate_subexp_standard) [OP_OBJC_MSGCALL]: Support 2009-09-29 00:48:32 +00:00
gold * testsuite/initpri1.c: Don't try to use constructor priorities if 2009-09-27 05:20:03 +00:00
gprof PR 10656 2009-09-25 09:57:50 +00:00
include merge from gcc 2009-09-26 00:01:16 +00:00
intl
ld missed entry 2009-09-28 07:14:37 +00:00
libdecnumber merge from gcc 2009-09-09 20:25:35 +00:00
libiberty merge from gcc 2009-09-23 17:59:27 +00:00
opcodes 2009-09-25 Michael Eager <eager@eagercon.com> 2009-09-25 19:59:51 +00:00
readline
sim 2009-09-23 Michael Eager <eager@eagercon.com> 2009-09-23 20:01:47 +00:00
texinfo
.cvsignore
ChangeLog * configure.ac: Pass any --cache-file=/dev/null option on to 2009-09-25 19:25:04 +00:00
compile
config-ml.in
config.guess * config.sub, config.guess: Update from upstream sources. 2009-09-23 09:51:31 +00:00
config.rpath
config.sub * config.sub, config.guess: Update from upstream sources. 2009-09-23 09:51:31 +00:00
configure * configure.ac: Pass any --cache-file=/dev/null option on to 2009-09-25 19:25:04 +00:00
configure.ac * configure.ac: Pass any --cache-file=/dev/null option on to 2009-09-25 19:25:04 +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
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.