3.3 problem of -fzero-initialized-in-bss

[Eric Botcazou]

> You mean the way that it wasn't the default in EGCS 1.1, and people didn't
> fix their software for it, and only after it had been enabled by default
> in 2.95 and 2.95.1, then disabled in 2.95.2, did people fix their
> software?  (And then it was reenabled by default in 3.0, but the warning
> option for broken code the 2.95.2 release notes vaguely offered didn't
> appear until 3.3.)  Not that it could particularly have been handled
> better, but the first release with it disabled didn't get code fixed.
> And "release with this feature turned on to get people to notice it, then
> turn it off temporarily for code to be fixed" is hardly a strategy to
> _plan_ to use, rather a response to an unforseen level of problems.

Ouch! I wasn't aware of this tumultuous history :-) Then my example was not 
well chosen, and the strategy might indeed not be very effective.

-- 
Eric Botcazou