[PATCH] D26960: [docs] Use x86_64 and i386 instead of x86 as arch for triples.

Florian Hahn via cfe-commits cfe-commits at lists.llvm.org
Tue Nov 22 03:23:18 PST 2016

fhahn created this revision.
fhahn added reviewers: rengolin, silvas.
fhahn added a subscriber: cfe-commits.

x86 is not a valid arch for target triples, but x86_64 and i386 are.



Index: docs/CrossCompilation.rst
--- docs/CrossCompilation.rst
+++ docs/CrossCompilation.rst
@@ -78,14 +78,14 @@
 on when assembling or linking.
 The triple has the general format ``<arch><sub>-<vendor>-<sys>-<abi>``, where:
- * ``arch`` = ``x86``, ``arm``, ``thumb``, ``mips``, etc.
+ * ``arch`` = ``x86_64``, ``i386``, ``arm``, ``thumb``, ``mips``, etc.
  * ``sub`` = for ex. on ARM: ``v5``, ``v6m``, ``v7a``, ``v7m``, etc.
  * ``vendor`` = ``pc``, ``apple``, ``nvidia``, ``ibm``, etc.
  * ``sys`` = ``none``, ``linux``, ``win32``, ``darwin``, ``cuda``, etc.
  * ``abi`` = ``eabi``, ``gnu``, ``android``, ``macho``, ``elf``, etc.
 The sub-architecture options are available for their own architectures,
-of course, so "x86v7a" doesn't make sense. The vendor needs to be 
+of course, so "x86v7a" doesn't make sense. The vendor needs to be
 specified only if there's a relevant change, for instance between PC
 and Apple. Most of the time it can be omitted (and Unknown)
 will be assumed, which sets the defaults for the specified architecture.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: D26960.78842.patch
Type: text/x-patch
Size: 1117 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20161122/4f8285fd/attachment.bin>

More information about the cfe-commits mailing list