[LLVMdev] Target-specific defaults for LLVM tools?

Joerg Sonnenberger joerg at britannica.bec.de
Tue Mar 17 15:21:58 PDT 2015

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.


More information about the llvm-dev mailing list