On Wed, May 2, 2012 at 12:03 PM, Alexander Monakov wrote:
>
>
> On Wed, 2 May 2012, Richard Guenther wrote:
>
>> That's surely too coarse - you will warn about options that _will_
>> have an effect.
>> There is currently no easy way to glob all affected options.
>
> Yeah, that's unfortunate. Do w
On Wed, 2 May 2012, Richard Guenther wrote:
> That's surely too coarse - you will warn about options that _will_
> have an effect.
> There is currently no easy way to glob all affected options.
Yeah, that's unfortunate. Do we want to have a separate flag
(CL_OPTIMIZATION_O0) to mark such optio
On Sat, Apr 28, 2012 at 4:48 PM, Alexander Monakov wrote:
>
> Looks like people who want to play with optimization options are still tripped
> by the fact that optimizations are not enabled unless -O is given (even though
> it's documented in the manual now). Can we add a warning for that like be
