[LLVMdev] Disabling certain optimizations at -O1?

[Evgeniy Stepanov]

Could we move this setting to function attributes?
We already have OptimizeForSize / MinSize there, but not the other opt
levels. We also have OptimizeNone, which seems to be completely
unused.
This would let us support __attribute__((optimize())) in the future,
which is currently ignored.
Another example would be an LTO link of objects compiled with
different optimization settings. I'm not sure if anyone would want
this in practice.


On Thu, Nov 28, 2013 at 5:41 PM, Renato Golin <renato.golin at linaro.org> wrote:
> On 28 November 2013 13:31, David Tweed <david.tweed at gmail.com> wrote:
>> Indeed, a most of the bugs which
>> really need a debugger are manifest in big applications where even a
>> non-debug build can be very "not simple".)
>
> My example was a very crude example of simplicity. But the more
> complex your application is, the simpler you want the compiler to be
> for a debug session.
>
> cheers,
> --renato
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev