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
This commit is contained in:
Chris Lattner 2010-10-28 02:22:02 +00:00
parent 9e08ee5d16
commit 219ddf5626

View File

@ -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>
<!-- _______________________________________________________________________ -->