Fix typo in build flags documentation
This commit is contained in:
parent
faa1ad44f7
commit
5b96b31cac
|
@ -159,8 +159,8 @@ not), but their selection depends on the architecture:
|
||||||
vulnerabilities can result where the stack overlaps with the heap,
|
vulnerabilities can result where the stack overlaps with the heap,
|
||||||
or thread stacks spill into other regions of memory.) This flag is
|
or thread stacks spill into other regions of memory.) This flag is
|
||||||
fully ABI-compatible and has adds very little run-time overhead, but
|
fully ABI-compatible and has adds very little run-time overhead, but
|
||||||
is only on certain architectures (currently aarch64, i386, ppc64,
|
is only available on certain architectures (currently aarch64, i386,
|
||||||
ppc64le, s390x, x86-64).
|
ppc64, ppc64le, s390x, x86-64).
|
||||||
* `-m64` and `-m32`: Some GCC builds support both 32-bit and 64-bit in
|
* `-m64` and `-m32`: Some GCC builds support both 32-bit and 64-bit in
|
||||||
the same compilation. For such architectures, the RPM build process
|
the same compilation. For such architectures, the RPM build process
|
||||||
explicitly selects the architecture variant by passing this compiler
|
explicitly selects the architecture variant by passing this compiler
|
||||||
|
|
Loading…
Reference in New Issue