d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix some formatting issues, bump .Dd to today's date, don't use

Browse Source 
contractions, and make igor almost happy with this (two issues are
false positives, and I'm not sure a synopsis makes sense).

Sponsored by: Netflix
This commit is contained in:
imp 2017-11-15 23:51:17 +00:00
parent a645e5aac5
commit a21132df63
1 changed files with 12 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
share/man/man7/arch.7
View File

@ -26,7 +26,7 @@
.\"
.\" $FreeBSD$
.\"
.Dd May 16, 2017
.Dd November 15, 2017
.Dt ARCH 7
.Os
.Sh NAME
@ -68,7 +68,7 @@ and
.Vt ptrdiff_t
should be avoided.
.Pp
On some architectures, e.g.
On some architectures, e.g.,
.Dv sparc64 ,
.Dv powerpc
and AIM variants of
@ -367,7 +367,7 @@ It is often the same as
just as one CPU architecture can be implemented by many different
hardware platforms, one hardware platform may support multiple CPU
architecture family members, though with different binaries.
For example,
For example,
.Dv MACHINE
of i386 supported the IBM-AT hardware platform while the
.Dv MACHINE
@ -393,12 +393,12 @@ integers (endian).
It may also encode a variation in the size of the integer or pointer.
It may also encode a ISA revision.
It may also encode hard versus soft floating point ABI and usage.
It may also encode a variant ABI when there other factors don't
It may also encode a variant ABI when there other factors do not
uniquely define the ABI (eg, MIPS' n32 ABI).
It, along with
.Dv MACHINE, define the ABI used by the system.
For example, the MIPS CPU processor family supports 9 different
combinations encoding pointer size, endian and hard vs soft float (for
combinations encoding pointer size, endian and hard versus soft float (for
8 combinations) as well as N32 (which only ever had one variation of
all these).
Generally, the plain CPU name specifies the most common (or at least
@ -429,15 +429,18 @@ framework).
to build.
It is used to optimize the build for a specific CPU / core that the
binaries run on.
Generally, this doesn't change the ABI, though it can be a fine line
Generally, this does not change the ABI, though it can be a fine line
between optimization for specific cases.
.It Dv TARGET Used to set Dv MACHINE in the top level Makefile for cross building.
.It Dv TARGET Used to set
.Dv MACHINE
in the top level Makefile for cross building.
Unused outside of that scope.
It is not passed down to the rest of the build.
Makefiles outside of the top level shouldn't use it at all (though
Makefiles outside of the top level should not use it at all (though
some have their own private copy for hysterical raisons).
.It Dv TARGET_ARCH Used to set
.Dv MACHINE_ARCH by the top level Makefile for cross building.
.Dv MACHINE_ARCH
by the top level Makefile for cross building.
Like
.Dv TARGET , it is unused outside of that scope.
.El