search for: llvm_set_machine_options

Chris Lattner wrote: > On Dec 1, 2011, at 5:23 PM, Nick Lewycky wrote: >>> Instead of adding a bunch of instance variables (+ getters/setters) into TargetMachine, why not make TargetOptions be a class, and have TM contain an instance of it? >> >> That works too, it makes little difference to me. One reason is that >> most references to these globals are inside classes

> If we can decide the way we want the options passed, I can take a stab > at it (or more likely Viktor will). The linker has a -plugin-opt option. You probably do something like -fplugin-opt=-mcpu= > I'd expect that gold will need an option that tells it that some > following option or options are to be passed to the plugin. The plugin > API will need to pass these flags

On Mon, Oct 5, 2009 at 8:04 PM, Rafael Espindola <espindola at google.com> wrote: >> I have no idea how to reduce this. >> >> Configure llvm-gcc for "arm-eabi" and use "--with-cpu=cortex-a8 >> --with-fpu=neon --with-abi=aapcs --with-float=hard". The triple in the >> bitcode will be "armv7-eabi" but the actual CPU subtarget won't