[LLVMdev] Target-specific defaults for LLVM tools?

Jonathan Roelofs jonathan at codesourcery.com
Tue Mar 17 14:31:48 PDT 2015

On 3/17/15 3:19 PM, Steve King wrote:
> Doesn't count for much, but I'm sympathetic to Dario's concern with
> cl::opt and clang defaults.  In one large out-of-tree project,
> colleagues decided to create their own driver to handle the required
> customization of the build process and options.
> 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

Jon Roelofs
jonathan at codesourcery.com
CodeSourcery / Mentor Embedded

More information about the llvm-dev mailing list