https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93763
--- Comment #9 from Arseny Solokha <asolokha at gmx dot com> --- (In reply to David Binderman from comment #8) > (In reply to CVS Commits from comment #7) > > Seems the test has been badly reduced (if the original doesn't emit > > warnings, it is always better in the reduction script avoid introducing > > new ones). > > I am no expert at creduce. Any guidance on suitable flags for this > case, or indeed the general case, would be most welcome. > > Should, for instance, -std=xyz flags be preserved ? Sorry for intervening. If you ask me, I have this in my reduction script: $GCCBINARY_GOOD -w -c $GCCOPTS_GOOD $INPUTFILE || exit 1 timeout 8 $GCCBINARY_BAD -w -c $GCCOPTS_BAD $INPUTFILE > $OUTPUTFILE 2>&1 && exit 1 where $GCCBINARY_BAD obviously corresponds to a version that has an issue in question and $GCCBINARY_GOOD to a version that doesn't, similarly for the sets of flags. It works in most cases where ICEs happen on inherently valid code.
