No description
Find a file
Keith Seitz cec808ecec * gdb.cp/cp-relocate.exp: Remove single-quoting of C++ methods.
* gdb.cp/cplusfuncs.cc (dm_type_short): New function.
        (dm_type_long): New function.
        (dm_type_unsigned_short): New function.
        (dm_type_unsigned_long): New function.
        (myint): New typedef.
        * gdb.cp/cplusfuncs.exp (probe_demangler): Add tests for short,
        long, unsigned shor and long, operator char*, and typedef.
        (test_lookup_operator_functions): Add operator char* test.
        (test_paddr_operator_functions): Likewise.
        (test_paddr_overloaded_functions): Use probe values for
        short, long, and unsigned short and long.
        (test_paddr_hairy_functions): If the demangler probe detected
        gdb type printers, "expect" them. Otherwise "expect" the v2 or v3
        demangler.
        * gdb.cp/expand-sals.exp: Backtrace may contain class names.
        * gdb.cp/member-ptr.exp: Refine expected result for "print pmf"
        and "print null_pmf".
        Add test "ptype a.*pmf".
        * gdb.cp/overload.exp: Allow optional "int" to appear with
        "short" and "long".
        * gdb.cp/ovldbreak.exp: Use append to construct super-duper
        long expect value for men_overload1arg.
        Allow "int" to appear with "short" and "long".
        When testing "info break", add argument for main (void).
        Also allow "int" to appear with "short" and "long".
        Ditto with "unsigned" and "long long".
	* gdb.java/jmain.exp: Do not enclose methods names in single
	quotes.
	* gdb.java/jmisc.exp: Likewise.
	* gdb.java/jprint.exp: Likewise.
	* gdb.python/py-symbol.exp: Update expected "linkage_name" value.

	From Jan Kratochvil  <jan.kratochvil@redhat.com>:
	* gdb.cp/exception.exp (backtrace after first throw)
	(backtrace after second throw): Allow a namespace before __cxa_throw.
	(backtrace after first catch, backtrace after second catch): Allow
	a namespace before __cxa_begin_catch.

	* gdb.cp/cpexprs.exp: New file.
	* gdb.cp/cpexprs.cc: New file.

	From Daniel Jacobowitz  <dan@codesourcery.com>
	* gdb.cp/cpexprs.exp (escape): Delete.  Change all callers
	to use string_to_regexp.
	(ctor, dtor): New functions.  Use them to match constructor
	and destructor function types.
	(Top level): Use runto_main.
2010-03-09 18:08:05 +00:00
bfd daily update 2010-03-08 23:00:18 +00:00
binutils include: 2010-03-05 21:04:59 +00:00
config Sync from gcc mainline. 2010-02-15 10:37:55 +00:00
cpu * m32r.cpu (HASH-PREFIX): Delete. 2010-02-12 04:38:21 +00:00
elfcpp include: 2010-03-05 21:04:59 +00:00
etc
gas Add tests for PR gas/9966 and PR gas/11356. 2010-03-09 02:00:58 +00:00
gdb * gdb.cp/cp-relocate.exp: Remove single-quoting of C++ methods. 2010-03-09 18:08:05 +00:00
gold 2010-03-08 Doug Kwan <dougkwan@google.com> 2010-03-08 22:15:16 +00:00
gprof Updated Vietnamese translation. 2010-02-15 10:09:39 +00:00
include include: 2010-03-05 21:04:59 +00:00
intl
ld ld: 2010-03-05 19:49:00 +00:00
libdecnumber merge from gcc 2010-01-05 21:10:30 +00:00
libiberty merge from gcc 2010-02-04 17:08:54 +00:00
opcodes * ppc-dis.c (ppc_opts): Add PPC_OPCODE_E500MC for "e500mc64". 2010-02-25 01:00:13 +00:00
readline
sim sim/moxie/ 2010-02-27 01:24:37 +00:00
texinfo
.cvsignore
ChangeLog PR libstdc++/32499 2010-03-04 17:12:46 +00:00
compile
config-ml.in
config.guess * config.sub, config.guess: Update from upstream sources. 2009-12-18 03:39:58 +00:00
config.rpath
config.sub * config.sub, config.guess: Update from upstream sources. 2009-12-18 03:39:58 +00:00
configure PR libstdc++/32499 2010-03-04 17:12:46 +00:00
configure.ac PR libstdc++/32499 2010-03-04 17:12:46 +00:00
COPYING
COPYING.LIB
COPYING.LIBGLOSS 2009-12-17 Jeff Johnston <jjohnstn@redhat.com> 2009-12-17 21:12:49 +00:00
COPYING.NEWLIB 2009-12-17 Jeff Johnston <jjohnstn@redhat.com> 2009-12-17 21:12:49 +00:00
COPYING3
COPYING3.LIB
depcomp
djunpack.bat
install-sh
libtool.m4 Sync Libtool from GCC. 2010-01-09 21:11:44 +00:00
ltgcc.m4
ltmain.sh Sync Libtool from GCC. 2010-01-09 21:11:44 +00:00
ltoptions.m4 Sync Libtool from GCC. 2010-01-09 21:11:44 +00:00
ltsugar.m4
ltversion.m4 Sync Libtool from GCC. 2010-01-09 21:11:44 +00:00
lt~obsolete.m4 Sync Libtool from GCC. 2010-01-09 21:11:44 +00:00
MAINTAINERS
Makefile.def gcc PR libstdc++/36101, gcc PR libstdc++/42813 2010-01-22 16:28:25 +00:00
Makefile.in PR 11238 2010-02-17 10:05:51 +00:00
Makefile.tpl * Makefile.tpl: Use "-exec rm {}" rather than "-delete" to delete 2010-02-17 11:02:54 +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.