[LLVMdev] Target-specific defaults for LLVM tools?

Steve King steve at metrokings.com
Tue Mar 17 16:35:07 PDT 2015

Clang correctly assembled a .s file when using the -integrated-as
option.  Thanks, that is news to me!  However, without -integrated-as,
clang invoked 'as', which won't work for a GNU-less target.  Accepting
assembler invocation as a good case study for target specific clang
defaults, what is the proper solution?

On Tue, Mar 17, 2015 at 3:21 PM, Joerg Sonnenberger
<joerg at britannica.bec.de> wrote:
> On Tue, Mar 17, 2015 at 03:00:48PM -0700, Steve King wrote:
>> >> If clang is the user's one stop shop, here's one such cross compiler
>> >> example I'd like to understand better:  GNU binutils has no clue of my
>> >> target.  Instead of trying to use gas, how should GNU-less targets
>> >> enable clang invoke llvm-mc to assemble?
>> >>
>> > -fintegrated-as / -fno-integrated-as
>> I tried, but integrated-as was impractical due to too many possible
>> machine code matches for a given assembly statement.  So, the compiler
>> deals in pseudos and emits .s files.  If the integrated assembler
>> could accept an assembly string instead of an mcinst, I'd be in
>> business.
>> Regardless, users could pass .s files on the command line and Clang
>> would still need to call llvm-mc with the right options.
> You don't make sense to me. IAS uses the same parser as llvm-mc.
> Joerg
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

More information about the llvm-dev mailing list