On Fri, May 29, 2009 at 09:02:23AM -0700, Steve Ellcey wrote:
> While looking into PR 37565 I began to wonder if we need to modify how
> we handle optimization flag handling. Currently we have
> OVERRIDE_OPTIONS, C_COMMON_OVERRIDE_OPTIONS, and OPTIMIZATION_OPTIONS to
> set or override the optimiza
Steve Ellcey writes:
> On Fri, 2009-05-29 at 09:38 -0700, Ian Lance Taylor wrote:
>> Steve Ellcey writes:
>>
>> > So instead of
>> >if (flag_var_tracking)
>> > we would have
>> >if (targetm.get_optimization_flag_value(OPT_fvar_tracking))
>>
>> I don't particularly want to have to make
On Fri, 2009-05-29 at 16:56 +, Joseph S. Myers wrote:
> I don't really feel that either the original proposal or this one is any
> cleaner than what we have right now, and the original proposal is at least
> simpler. As neither really addresses the general issues with how options
> are han
On Fri, 2009-05-29 at 09:38 -0700, Ian Lance Taylor wrote:
> Steve Ellcey writes:
>
> > So instead of
> > if (flag_var_tracking)
> > we would have
> > if (targetm.get_optimization_flag_value(OPT_fvar_tracking))
>
> I don't particularly want to have to make an indirect function call
> ev
Ian Lance Taylor wrote:
> Steve Ellcey writes:
>
>> So instead of
>> if (flag_var_tracking)
>> we would have
>> if (targetm.get_optimization_flag_value(OPT_fvar_tracking))
>
> I don't particularly want to have to make an indirect function call
> every time we check a flag. I don't se
On Fri, 29 May 2009, Steve Ellcey wrote:
> While looking into PR 37565 I began to wonder if we need to modify how
> we handle optimization flag handling. Currently we have
> OVERRIDE_OPTIONS, C_COMMON_OVERRIDE_OPTIONS, and OPTIMIZATION_OPTIONS to
> set or override the optimization flags a user gi
Steve Ellcey writes:
> So instead of
> if (flag_var_tracking)
> we would have
> if (targetm.get_optimization_flag_value(OPT_fvar_tracking))
I don't particularly want to have to make an indirect function call
every time we check a flag. I don't see why we should check every time
whe
While looking into PR 37565 I began to wonder if we need to modify how
we handle optimization flag handling. Currently we have
OVERRIDE_OPTIONS, C_COMMON_OVERRIDE_OPTIONS, and OPTIMIZATION_OPTIONS to
set or override the optimization flags a user gives. One proposal to
fix 37565 was to split OVERR
