NetBSD/gnu
christos fab093cf4d Apply patch from the RedHat CVS tree. Avoids issue with -O3 using the
wrong registers with some opcodes, the error is:
Error: Illegal operands: There are only 32 single precision f registers; [0-31]
And the code to cause this is:
	return (cond) ? x : -x;
where x is double.
2005-04-24 23:53:18 +00:00
..
dist Apply patch from the RedHat CVS tree. Avoids issue with -O3 using the 2005-04-24 23:53:18 +00:00
lib Enable wide character support for the rest of the archs (i386 is already done). 2005-03-31 03:17:02 +00:00
libexec Add (unsigned char) cast to ctype functions 2004-11-05 19:56:34 +00:00
usr.bin another place where 17 -> 20 needs to be changed. 2005-04-20 02:00:45 +00:00
usr.sbin resolve conflicts, pull 8.13.3 to head, make it build 2005-03-15 02:14:15 +00:00
Makefile Install the MMX/SSE/Altivec include files that gcc provides. 2003-12-05 18:56:11 +00:00
README netbsd.org -> NetBSD.org 2003-12-04 23:32:37 +00:00

README

$NetBSD: README,v 1.5 2003/12/04 23:32:37 keihan Exp $

Organization of Sources:

This directory hierarchy is using a new organization that
separates the GNU sources from the BSD-style infrastructure
used to build the GNU sources.  The GNU sources are kept in
the standard GNU source tree layout under:

	dist/*

The build infrastructure uses the normal BSD way under:

	lib/*
	usr.bin/*

The makefiles in the above hierarchy will "reach over" into
the GNU sources (src/gnu/dist) for everything they need.


Maintenance Strategy:

The sources under src/gnu/dist are generally a combination of
some published distribution plus changes that we submit to the
maintainers and that are not yet published by them.  There are
a few files that are never expected to be submitted to the FSF,
(i.e. BSD-style makefiles and such) and those generally should
stay in src/gnu/lib or src/gnu/usr.bin (the BSD build areas).

Make sure all changes made to the GNU sources are submitted to
the appropriate maintainer, but only after coordinating with the
NetBSD maintainers by sending your proposed submission to the
<tech-toolchain@NetBSD.org> mailing list.  Only send the changes
to the third-party maintainers after consensus has been reached.