On 5/2/24 12:59 PM, Vineet Gupta wrote:
This is no logic change (but technically still a functional change).

Ran into this when stepping thru combine code.
@newpat has some random garbage for a bit until it is actually set.
With the fix it remains 0 until actually set.

gcc/ChangeLog:
        * combine.cc (try_combine): Initialize newpat.
Isn't the same true even after this change if you turn on the optimizer? And isn't the same true for many other objects that are initialized lazily?

Ultimately I'll defer to Segher on this.

jeff

Reply via email to