https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99824
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> --- (In reply to Martin Liška from comment #6) > > diff --git a/gcc/stor-layout.c b/gcc/stor-layout.c > > index 784f131ebb8..94b8b21c7a8 100644 > > --- a/gcc/stor-layout.c > > +++ b/gcc/stor-layout.c > > @@ -2838,6 +2838,8 @@ set_min_and_max_values_for_integral_type (tree type, > > if (precision < 1) > > return; > > > > + gcc_assert (precision <= WIDE_INT_MAX_PRECISION); > > + > > TYPE_MIN_VALUE (type) > > = wide_int_to_tree (type, wi::min_value (precision, sgn)); > > TYPE_MAX_VALUE (type) > > > > should uncover any similar issue and eventually allow producing smaller > > testcases. > > Where would you expect the assert to be triggered? In LTO/non-LTO mode? Eventually in both. The assert also triggers with the cited change reverted so I do think the issue is latent.
