Some fields in other ELF structures have flags
and values that have platform-specific meanings;
the interpretation of those fields is determined by the value of this byte.
-E.g.:
+For example:
.\" .Bl -tag -width "ELFOSABI_STANDALONE" -compact
.RS 12
.TP 20
.TP
.IR e_machine
This member specifies the required architecture for an individual file.
-E.g.:
+For example:
.RS 12
.\" .Bl -tag -width "EM_MIPS_RS4_BE" -compact
.TP 12
will include the
.BR SHF_ALLOC
bit.
-Otherwise the bit will be off.
+Otherwise, the bit will be off.
By convention,
"NAME"
is supplied by the section to which the relocations apply.
will include the
.BR SHF_ALLOC
bit.
-Otherwise the bit will be off.
+Otherwise, the bit will be off.
By convention,
"NAME"
is supplied by the section to which the relocations apply.
will include the
.BR SHF_ALLOC
bit.
-Otherwise the bit will be off.
+Otherwise, the bit will be off.
This section is of type
.BR SHT_STRTAB .
.TP
the
.BR SHF_ALLOC
bit.
-Otherwise the bit will be off.
+Otherwise, the bit will be off.
This section is of type
.BR SHT_SYMTAB .
.TP
.IR "System V Application Binary Interface AMD64 Architecture Processor Supplement" .
.PP
.SH COLOPHON
-This page is part of release 3.65 of the Linux
+This page is part of release 3.68 of the Linux
.I man-pages
project.
A description of the project,
-and information about reporting bugs,
+information about reporting bugs,
+and the latest version of this page,
can be found at
\%http://www.kernel.org/doc/man\-pages/.