forked from OSchip/llvm-project
clarify that not having the ".o file writing" feature
doesn't mean that you can't get a .o file. Apparently this is confusing :) llvm-svn: 117523
This commit is contained in:
parent
4935b45d74
commit
15597538ae
|
@ -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>
|
||||
|
||||
<!-- _______________________________________________________________________ -->
|
||||
|
|
Loading…
Reference in New Issue