Go to file
Richard Kenner a0c3333844 alias.c (record_component_aliases): New function.
* alias.c (record_component_aliases): New function.
	* tree.h: Clean up some declarations and comments.
	(record_component_aliases): New declaration.
	* tree.c (get_alias_set): If type and has alias set, use it.

From-SVN: r34078
2000-05-22 06:51:28 -04:00
boehm-gc
config
contrib Oops, removed `Reported by' comment 2000-05-18 05:32:06 +00:00
etc * standards.texi, make-stds.texi: Update to FSF version of May 13. 2000-05-18 07:17:15 +00:00
gcc alias.c (record_component_aliases): New function. 2000-05-22 06:51:28 -04:00
include
INSTALL
libchill
libf2c Daily bump. 2000-05-22 01:45:07 -06:00
libffi
libiberty * xmalloc.c: Include config.h for HAVE_SBRK definition. 2000-05-18 16:48:34 -06:00
libio
libjava * libjava.compile/PR234.java: New file. For PR gcj/234. 2000-05-22 05:14:38 +00:00
libobjc
libstdc++
libstdc++-v3 acinclude.m4: Clean up comments on newer checks. 2000-05-19 19:55:50 +00:00
texinfo
zlib
.cvsignore
ChangeLog * configure.in (hppa*64*-*-*): Do build ld for this configuration. 2000-05-18 11:04:14 -06:00
config-ml.in
config.guess
config.if
config.sub
configure
configure.in * configure.in (hppa*64*-*-*): Do build ld for this configuration. 2000-05-18 11:04:14 -06:00
COPYING
COPYING.LIB
install-sh
ltconfig
ltmain.sh
MAINTAINERS
Makefile.in Makefile.in (configure-target-libiberty): Depend on configure-target-newlib. 2000-05-18 04:15:51 +00:00
missing
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.