[LLVMdev] Target-specific defaults for LLVM tools?

Jonathan Roelofs jonathan at codesourcery.com
Tue Mar 17 15:17:33 PDT 2015

On 3/17/15 4:00 PM, 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.
Which arch is this?
> Regardless, users could pass .s files on the command line and Clang
> would still need to call llvm-mc with the right options.
That's sort of what `clang -cc1as` does already when you do: `clang 
foo.s -integrated-as`.

Jon Roelofs
jonathan at codesourcery.com
CodeSourcery / Mentor Embedded

More information about the llvm-dev mailing list