https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99989
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #1) > This isn't the first PR where wide_ints are a problem for -W*uninitialized > warnings. The primary problem is that generic_wide_int default ctor does > nothing and so does wide_int_storage default ctor, so keeps everything > uninitialized. > Do we want some non-default ctor say with some magic enum or whatever > argument that would zero initialize the whole storage? 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.
