Add new Multi-Architecture development policy (posted previously by

Warner) to the Committer's Handbook.
This commit is contained in:
Robert Watson 2002-09-19 18:32:24 +00:00
parent a0a1ffbb85
commit 89dc80e98a
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=14327

View file

@ -579,11 +579,11 @@
</itemizedlist>
<para>You will almost certainly get a conflict because
of the <literal>$Id: article.sgml,v 1.133 2002-09-14 20:57:12 blackend Exp $</literal> (or in FreeBSD's case,
of the <literal>$Id: article.sgml,v 1.134 2002-09-19 18:32:24 rwatson Exp $</literal> (or in FreeBSD's case,
<literal>$<!-- stop expansion -->FreeBSD<!-- stop expansion -->$</literal>) lines, so you will have to edit
the file to resolve the conflict (remove the marker lines and
the second <literal>$Id: article.sgml,v 1.133 2002-09-14 20:57:12 blackend Exp $</literal> line, leaving the original
<literal>$Id: article.sgml,v 1.133 2002-09-14 20:57:12 blackend Exp $</literal> line intact).</para>
the second <literal>$Id: article.sgml,v 1.134 2002-09-19 18:32:24 rwatson Exp $</literal> line, leaving the original
<literal>$Id: article.sgml,v 1.134 2002-09-19 18:32:24 rwatson Exp $</literal> line intact).</para>
</listitem>
<listitem>
@ -1850,6 +1850,41 @@ docs:Documentation Bug:nik:</programlisting>
</orderedlist>
</sect2>
<sect2>
<title>Policy on Multiple Architectures</title>
<para>FreeBSD has added several new arch ports during the 5.0
release cycle and is truly no longer an i386-centric operating
system. In an effort to make it easier to keep FreeBSD portable
across the platforms we support, core has developed the following
mandate:</para>
<blockquote>
<para>Our 32 bit reference platform is i386, and our 64 bit
reference platform is sparc64. Major design work (including
major API and ABI changes) must prove itself on at least one
32 bit and at least one 64 bit platform, preferably the
primary reference platforms.</para>
</blockquote>
<para>The i386 and sparc64 platforms were chosen due to being more
readily availabile to developers and as representatives of more
diverse processor and system designs - big vs little endian,
register file vs register stack, different DMA and cache
implementations, hardware page tables vs software TLB management
etc.</para>
<para>While the Alpha is a 64 bit processor, it is a more
traditional processor design and does not provide as good a testbed
for many of the challenges that the other 64 bit platform ports
face. The ia64 platform has many of the same complications that
sparc64 has, but is still limited in availability to
developers.</para>
<para>We will continue to re-evaluate this policy as cost and
availability of the 64 bit platforms change.</para>
</sect2>
<sect2>
<title>Other Suggestions</title>