OpenE2K/gcc - gcc - Expired Mentality Git

Go to file

Jeffrey A Law 14fe6c707f m68k.md (xordi3, anddi3): These patterns are not available on the coldfire. * m68k.md (xordi3, anddi3): These patterns are not available on the coldfire. From-SVN: r28524		1999-08-05 00:22:16 -06:00
boehm-gc	Removed extra ';;'	1999-08-04 20:57:53 +00:00
config
contrib	egcs_update (files_and_dependencies): Fixed typo in gcc/cstamp-h.in.	1999-07-28 17:52:02 +00:00
etc
gcc	m68k.md (xordi3, anddi3): These patterns are not available on the coldfire.	1999-08-05 00:22:16 -06:00
include	* splay-tree.h (splay_tree_insert): Return the new node.	1999-08-02 05:54:50 +00:00
INSTALL
libchill
libf2c	Daily bump.	1999-08-04 01:46:10 -06:00
libiberty	* splay-tree.h (splay_tree_insert): Return the new node.	1999-08-02 05:54:50 +00:00
libio
libjava	configure.in: Also do AC_SUBST for DIVIDESPEC.	1999-08-05 05:21:44 +00:00
libobjc
libstdc++	* Makefile.in (INTERFACE): Bump to 3.	1999-07-17 23:52:37 -06:00
texinfo
zlib	* aclocal.m4, configure: Rebuilt for new libtool.	1999-08-03 03:19:52 +00:00
.cvsignore
ChangeLog	* config.sub (vxworks case): Use os=-vxworks, not os=vxworks.	1999-08-04 02:07:57 -06:00
config-ml.in
config.guess
config.if
config.sub	* config.sub (vxworks case): Use os=-vxworks, not os=vxworks.	1999-08-04 02:07:57 -06:00
configure
configure.in
COPYING
COPYING.LIB
install-sh
ltconfig
ltmain.sh
MAINTAINERS	Update my email address	1999-07-26 16:31:02 +00:00
Makefile.in
missing
mkinstalldirs
move-if-change
README
symlink-tree
ylwrap

README

		   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.