[Bug middle-end/99989] [11 regression] False maybe-uninitialized warning breaks bootstrap on riscv64

[rsandifo at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99989

--- Comment #3 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #2)
> I don't think we want any initialization unless we invent an explicitely
> "uninitialized" state.  Note that wide-int storage is large - I suppose
> initializing precision to zero could be done, but I'd avoid initializing
> the storage.
FWIW, I agree we shouldn't initialise unless we have a sensible value
to initialise to.  The problem is that a zero precision has no meaning,
but if we initialise to it anyway, it's an extra state that all wide_int
accessors have to assert on.