diff options
author | Chris Lattner <sabre@nondot.org> | 2010-10-28 02:22:02 +0000 |
---|---|---|
committer | Chris Lattner <sabre@nondot.org> | 2010-10-28 02:22:02 +0000 |
commit | 219ddf5626c526da298f255edb166f2ba5b75b1f (patch) | |
tree | 14adc396f2c8e077e8a3502ffff020b7d879dd51 /docs/CodeGenerator.html | |
parent | 9e08ee5d16b596078e20787f0b5f36121f099333 (diff) |
clarify that not having the ".o file writing" feature
doesn't mean that you can't get a .o file. Apparently
this is confusing :)
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@117523 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/CodeGenerator.html')
-rw-r--r-- | docs/CodeGenerator.html | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/CodeGenerator.html b/docs/CodeGenerator.html index f811998eb6..3e0ac1be34 100644 --- a/docs/CodeGenerator.html +++ b/docs/CodeGenerator.html @@ -2160,6 +2160,10 @@ ELF, and/or COFF) files directly from the target. Note that the target also must include an assembly parser and general inline assembly support for full inline assembly support in the .o writer.</p> +<p>Targets that don't support this feature can obviously still write out .o +files, they just rely on having an external assembler to translate from a .s +file to a .o file (as is the case for many C compilers).</p> + </div> <!-- _______________________________________________________________________ --> |