Ian Lance Taylor wrote:
> Steve Ellcey <s...@cup.hp.com> 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
> when we can determine the value once when the compiler starts.
The PR is about the interaction between backend optimisation overrides and
"pragma GCC optimize" and the __optimize__ attribute. Since these change as
compilation proceeds, the backend's choices at compiler startup may need to be
revisited.
However I also feel it's a bit of a top-heavy solution. What's wrong with
the simple ONCE/ALWAYS split proposed by HJ in comment #8?
cheers,
DaveK
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37565#c8
