a67241065b
these GCC PR's: c++/17763 middle-end/25445 c++/27177 target/28307 rtl-optimization/30113 target/31331 c++/31941 rtl-optimization/31944 tree-optimization/31966 c++/32112 c++/32113 rtl-optimization/32450 target/32506 tree-optimization/32533 target/32641 target/32660 tree-optimization/32681 middle-end/32912 c++/32992 tree-optimization/33142 target/33256 bootstrap/33418 c++/33744 driver/33772 rtl-optimization/33822 middle-end/33826 c++/33959 bootstrap/34003 middle-end/34030 middle-end/34130 rtl-optimization/34456 libgfortran/34699 c/34993 c++/35007 |
||
---|---|---|
.. | ||
dist | ||
lib | ||
usr.bin | ||
usr.sbin | ||
Makefile | ||
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.