Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/gnu
History
skrll 64001ed248 Our hppa userland space register convention isn't as flat as it needs to be 
for MASK_NO_SPACE_REGS. The assumption is that sr4-sr7 == process space
id, but we have sr7 = kernel space id (0). This was inherited from
OpenBSD.

If sr4-sr7 == process space id, then

        ldw     %r1(,%r2),%r3
and
        ldw     %r2(,%r1),%r3

are equivlent for all values of %r1 and %r2.

If the right compat stuff is in place we can change the space register
convention and turn MASK_NO_SPACE_REGS back on.
 		2006-09-22 13:11:57 +00:00
..
dist Our hppa userland space register convention isn't as flat as it needs to be 2006-09-22 13:11:57 +00:00
lib Bootstrap for ia64 2006-09-14 23:48:28 +00:00
libexec
…
usr.bin Do not use tabs in this file -- this breaks output. Use spaces instead. 2006-09-14 23:23:56 +00:00
usr.sbin Install aliases(5) from postfix, since the sendmail one is gone, 2006-09-19 20:10:22 +00:00
Makefile
…
README
…

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.