NetBSD/gnu
matt 58ad121651 Step 1 of getting gcc to generate VAX PIC code again. These steps are being
committed in "smallish" steps.  This step incorporates the switch to MEM_P,
REG_P, and CONST_INT_P.  Use bool/true/false where appropriate.  PRINT_OPERAND
moves from being a large macro in vax.h print_operand in vax.c.  Fix rtx cost
for a constant of 0.  This eliminates unneeded moves when setting to 0 would
be fine.

Lastly, include completely new (on by default) code for DImode move, addition,
and subtract.  This code is significantly faster and smaller that what existed
before.
2007-03-30 20:25:46 +00:00
..
dist Step 1 of getting gcc to generate VAX PIC code again. These steps are being 2007-03-30 20:25:46 +00:00
lib Honour ${CPUFLAGS} 2007-03-09 04:40:38 +00:00
usr.bin regenerate everything with fixed c++ math bits. 2007-03-01 01:57:15 +00:00
usr.sbin add -Wno-stack-protector because of the CMSG macro lossage. 2006-11-09 21:40:20 +00:00
Makefile goodbye uucp 2006-11-12 01:20:00 +00:00
README netbsd.org -> NetBSD.org 2003-12-04 23:32:37 +00:00

$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.