aedbc29a82
* FPU_MEMMULTI -- only include the FPU_FPA10 bit. * FPU_ARCH_VFP -- define, meaning "uses VFP-format layout". * FPU_FPA -- define short-hand for (FPU_CORE|FPU_FPA10). * FPU_DEFAULT -- FPU_ALL -> FPU_FPA. * Floating point instructions -- FPU_ALL -> FPU_FPA. * Also set F_SOFT_FLOAT if FPU_ARCH_VFP. * Set F_VFP_FLOAT if FPU_ARCH_VFP. * md_atof: lay out bytes properly if using VFP. * Accept -mfpu=softvfp. * For -mall, set the FPU part of cpu_variant to FPU_FPA, instead of FPU_ALL. |
||
---|---|---|
.. | ||
dist | ||
lib | ||
libexec | ||
usr.bin | ||
usr.sbin | ||
Makefile | ||
README |
$NetBSD: README,v 1.4 2002/09/22 09:47:56 wiz 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.