search for: menable

...gument '-disable-inlining'. Try: 'cc1 -help' (2). Does 'fplugin-arg-dragonegg-llvm-option' allow ONLY 'opt' options? (by llvm options does it mean only opt) (3). Depending on answer to (2), currently is there a way to pass llc options to dragonegg? For instance -menable-unsafe-math? $ gcc -fplugin=dragonegg.so -fplugin-arg-dragonegg-llvm-option='-menable-unsafe-math' foo.c -S cc1: Unknown command line argument '-menable-unsafe-math'. Try: 'cc1 -help' The case for passing 'llc' options stems from the requirement that code generat...

...gument '-disable-inlining'. Try: 'cc1 -help' (2). Does 'fplugin-arg-dragonegg-llvm-option' allow ONLY 'opt' options? (by llvm options does it mean only opt) (3). Depending on answer to (2), currently is there a way to pass llc options to dragonegg? For instance -menable-unsafe-math? $ gcc -fplugin=dragonegg.so -fplugin-arg-dragonegg-llvm-option='-menable-unsafe-math' foo.c -S cc1: Unknown command line argument '-menable-unsafe-math'. Try: 'cc1 -help' The case for passing 'llc' options stems from the requirement that code generat...

...mplementation doesn't do that, since the 'fast' IR-level flag still gets set. Motivation of this discussion: https://llvm.org/bugs/show_bug.cgi?id=27372#c2 As an aside, when '-ffast-math' is specified on the command-line, the following six switches are all passed to cc1: -menable-no-infs -menable-no-nans -fno-signed-zeros -freciprocal-math -fno-trapping-math -ffp-contract=fast and '-ffast-math' itself is also passed cc1 (the act of passing '-ffast-math' to cc1 results in the macro '__FAST_MATH__' being defined). When (for exampl...

...gets set. > > > Motivation of this discussion: > > https://llvm.org/bugs/show_bug.cgi?id=27372#c2 > > > As an aside, when '-ffast-math' is specified on the command-line, > > the > > > following six switches are all passed to cc1: > > > -menable-no-infs > > > -menable-no-nans > > > -fno-signed-zeros > > > -freciprocal-math > > > -fno-trapping-math > > > -ffp-contract=fast > > > and '-ffast-math' itself is also passed cc1 (the act of passing > > '-ffast-math'...

...e're > going to want a unified interface to all of them. I haven't applied your > patch to see what the IR changes look like here. > > With the patches applied, the attributes clang embeds in the IR look like this: $ clang -cc1 ... -mllvm -arm-long-calls -mllvm -arm-reserve-r9 -menable-no-nans attributes #0 = { nounwind readonly ssp "NoNaNsFPMath" "arm-long-calls"="1" "arm-reserve-r9"="1" "less-precise-fpmad"="false" "no-frame-pointer-elim"="true" "no-frame-pointer-elim-non-leaf"...

...e going to want a unified interface to all of them. I haven't applied your patch to see what the IR changes look like here. > > > With the patches applied, the attributes clang embeds in the IR look like this: > > $ clang -cc1 ... -mllvm -arm-long-calls -mllvm -arm-reserve-r9 -menable-no-nans > attributes #0 = { nounwind readonly ssp "NoNaNsFPMath" "arm-long-calls"="1" "arm-reserve-r9"="1" "less-precise-fpmad"="false" "no-frame-pointer-elim"="true" "no-frame-pointer-elim-non-leaf&qu...

...ified interface to all of them. I haven't applied your patch to see what the IR changes look like here. >> >> >> With the patches applied, the attributes clang embeds in the IR look like this: >> >> $ clang -cc1 ... -mllvm -arm-long-calls -mllvm -arm-reserve-r9 -menable-no-nans >> attributes #0 = { nounwind readonly ssp "NoNaNsFPMath" "arm-long-calls"="1" "arm-reserve-r9"="1" "less-precise-fpmad"="false" "no-frame-pointer-elim"="true" "no-frame-pointer-elim-non-lea...

...e IR changes look like here. >>>>> >>>>> >>>> With the patches applied, the attributes clang embeds in the IR look >>>> like this: >>>> >>>> $ clang -cc1 ... -mllvm -arm-long-calls -mllvm -arm-reserve-r9 >>>> -menable-no-nans >>>> >>>> attributes #0 = { nounwind readonly ssp "NoNaNsFPMath" >>>> "arm-long-calls"="1" "arm-reserve-r9"="1" "less-precise-fpmad"="false" >>>> "no-frame-pointer-elim...

...; >>>>>>> >>>>>> With the patches applied, the attributes clang embeds in the IR look >>>>>> like this: >>>>>> >>>>>> $ clang -cc1 ... -mllvm -arm-long-calls -mllvm -arm-reserve-r9 >>>>>> -menable-no-nans >>>>>> >>>>>> attributes #0 = { nounwind readonly ssp "NoNaNsFPMath" >>>>>> "arm-long-calls"="1" "arm-reserve-r9"="1" "less-precise-fpmad"="false" >>>>>...

...gt;>>>>> With the patches applied, the attributes clang embeds in the IR >>>>>>>> look like this: >>>>>>>> >>>>>>>> $ clang -cc1 ... -mllvm -arm-long-calls -mllvm -arm-reserve-r9 >>>>>>>> -menable-no-nans >>>>>>>> >>>>>>>> attributes #0 = { nounwind readonly ssp "NoNaNsFPMath" >>>>>>>> "arm-long-calls"="1" "arm-reserve-r9"="1" "less-precise-fpmad"="false&qu...

Updated patch is attached. Note this is just a work-in-progress patch and I plan to address the feedback comments later if this patch is in the right direction. This is how the command line options are parsed and used by the backend passes: 1. Tools such as clang and llc call cl::ParseCommandLineOptions. Any of the options that should be written to the bitcode as function or module attributes