From: Bill Wendling Date: Fri, 18 Oct 2013 23:41:25 +0000 (+0000) Subject: Write a simple description of the 'target triple' directive. This should be expanded... X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=4216b993caf5a5bb24c5308eda32242fd06aaaca;p=oota-llvm.git Write a simple description of the 'target triple' directive. This should be expanded. PR8976. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@193014 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/LangRef.rst b/docs/LangRef.rst index 2449e017520..b75c6b1b80f 100644 --- a/docs/LangRef.rst +++ b/docs/LangRef.rst @@ -1178,6 +1178,30 @@ don't have to specify the string. This will disable some optimizations that require precise layout information, but this also prevents those optimizations from introducing target specificity into the IR. +.. _langref_triple: + +Target Triple +------------- + +A module may specify a target triple string that describes the target +host. The syntax for the target triple is simply: + +.. code-block:: llvm + + target triple = "x86_64-apple-macosx10.7.0" + +The *target triple* string consists of a series of identifiers delimited +by the minus sign character ('-'). The canonical forms are: + +:: + + ARCHITECTURE-VENDOR-OPERATING_SYSTEM + ARCHITECTURE-VENDOR-OPERATING_SYSTEM-ENVIRONMENT + +This information is passed along to the backend so that it generates +code for the proper architecture. It's possible to override this on the +command line with the ``-mtriple`` command line option. + .. _pointeraliasing: Pointer Aliasing Rules