Binutils with MCST patches
Go to file
Jan Kratochvil 61ff14c69a gdb/
* stack.c (return_command <retval_exp>): New variables retval_expr
	and old_chain.  Inline parse_and_eval to initialize retval_expr.  Check
	RETVAL_EXPR for UNOP_CAST and set RETURN_TYPE to the RETURN_VALUE type
	if RETURN_TYPE is NULL.

gdb/doc/
	* gdb.texinfo (Returning): New description for missing debug info.

gdb/testsuite/
	* gdb.base/return-nodebug.exp, gdb.base/return-nodebug.c: New.
2009-03-15 09:19:40 +00:00
bfd * elf32-spu.c (build_stub): Correct icache set_id. 2009-03-15 03:28:51 +00:00
binutils bfd/ 2009-03-14 09:11:38 +00:00
config * config/tcl.m4 (SC_PATH_TCLCONFIG): Don't exit 0 if tclconfig fails. 2009-02-02 23:18:05 +00:00
cpu
elfcpp elfcpp:/ 2009-03-02 02:45:29 +00:00
etc bfd: 2009-02-03 15:54:05 +00:00
gas gas/testsuite/ 2009-03-14 09:37:18 +00:00
gdb gdb/ 2009-03-15 09:19:40 +00:00
gold * readsyms.cc (Read_symbols::incompatible_warning): New function. 2009-03-14 05:56:46 +00:00
gprof Updated Spanish translations. 2009-03-06 12:14:40 +00:00
include include/coff/ 2009-03-14 09:35:46 +00:00
intl
ld include/coff/ 2009-03-14 09:35:46 +00:00
libdecnumber merge from gcc 2009-02-10 16:18:42 +00:00
libiberty merge from gcc 2009-02-23 00:16:38 +00:00
opcodes Add Spanish translation to gold. 2009-03-10 09:21:01 +00:00
readline
sim * sim/cris/asm/opterr5.ms, sim/cris/asm/opterr4.ms, 2009-01-18 22:17:47 +00:00
texinfo
.cvsignore
ChangeLog Backport from git Libtool: 2009-03-01 18:57:19 +00:00
compile
config-ml.in
config.guess
config.rpath
config.sub
configure * configure.ac (ia64*-*-*vms*): Add case with no gdb or ld support. 2009-01-15 12:55:46 +00:00
configure.ac * configure.ac (ia64*-*-*vms*): Add case with no gdb or ld support. 2009-01-15 12:55:46 +00:00
COPYING
COPYING3
COPYING3.LIB
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB 2009-01-21 Jeff Johnston <jjohnstn@redhat.com> 2009-01-22 00:08:29 +00:00
depcomp
djunpack.bat
install-sh
libtool.m4 Backport from git Libtool: 2009-03-01 18:57:19 +00:00
lt~obsolete.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
MAINTAINERS
Makefile.def * Makefile.def (configure-opcodes): Depend on configure-libiberty. 2009-01-16 08:06:15 +00:00
Makefile.in * Makefile.tpl (stage_last): Define $r and $s before using 2009-02-05 15:45:55 +00:00
Makefile.tpl * Makefile.tpl (stage_last): Define $r and $s before using 2009-02-05 15:45:55 +00:00
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.