Go to file
Neil Booth 74f215d7e0 19960224-2.c, [...]: Update tests for new diagnostic messages.
* gcc.dg/cpp/19960224-2.c, 20000625-2.c, cxxcom2.c, directiv.c,
	endif.c, if-4.c, if-5.c, if-mop.c, macsyntx.c, paste2.c, paste6.c,
	paste8.c, redef2.c, strify2.c, strp1.c, tr-warn1.c, tr-warn3.c,
	tr-warn6.c, undef1.c, undef2.c, widestr1.c: Update tests for
	new diagnostic messages.

	* gcc.dg/cpp/macro3.c: New tests.

From-SVN: r37099
2000-10-28 18:01:40 +00:00
boehm-gc
config
contrib * gcc_build: Fix typos. 2000-10-26 01:18:12 +00:00
etc
gcc 19960224-2.c, [...]: Update tests for new diagnostic messages. 2000-10-28 18:01:40 +00:00
include
INSTALL
libchill
libf2c Daily bump. 2000-10-28 01:45:08 -06:00
libffi
libiberty Fix incorrect date in ChangeLog entry. 2000-10-23 18:11:23 +00:00
libio
libjava natGregorianCalendar.cc (computeFields): Set the isSet__ array elements to true. 2000-10-27 11:53:53 +00:00
libobjc
libstdc++ std_valarray.h (valarray::valarray): Use __valarray_copy, not __valarray_copy_construct. 2000-10-23 16:24:19 +00:00
libstdc++-v3 [multiple changes] 2000-10-27 12:31:37 +00:00
texinfo
zlib configure.in: Invoke AC_PROG_CPP unconditionally before conditional feature tests. 2000-10-25 18:07:29 +00:00
.cvsignore
ChangeLog
config-ml.in
config.guess
config.if
config.sub
configure
configure.in
COPYING
COPYING.LIB
djunpack.bat
install-sh
libtool.m4
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh
ltconfig
ltmain.sh
MAINTAINERS
Makefile.in
missing
mkdep
mkinstalldirs
move-if-change
README
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.


Check the INSTALL directory for detailed configuration and installation
instructions.


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.