https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103691
--- Comment #2 from Andrew Macleod <amacleod at redhat dot com> ---
Its triggering an assert in the gimple folder when trying to process:
# DEBUG D.4293 => &a[0]
The constructor shows:
static real(kind=4) a[0] = {[0 ... -1]=2.0e+0};
is that a range of 0 to -1? its triggering an assert in line 13314 of
fold_const:
gcc_checking_assert (wi::le_p (index, max_index, index_sgn));
it looks to be because max_index is less than index?
The referenced change causes this because it now calls gimple_fold on all stmts
instead of just ranger specific ones. I presume we are suppose to call fold on
debug stmts too?
