https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82982
--- Comment #8 from Will Schmidt <willschm at gcc dot gnu.org> --- (In reply to Will Schmidt from comment #6) > (In reply to Arseny Solokha from comment #5) > > (In reply to Will Schmidt from comment #4) > > > Tried to re-create locally, I've gotten two ICE's using the provided > > > testcode snippet, neither look quite like the originally reported issue. > > > > You are right. I also cannot reproduce the original issue anymore w/ > > r257975. > > Today I cannot get any ICE's out of this test. Wonder if things were fixed > up in the mean-time, or if I tickled a config option and managed to hide the > issue(s). Going to try a few more runs with older trees to see if I can > verify things are fixed. (In reply to Arseny Solokha from comment #7) > OK, the original issue still reproduces for the powerpc-e500v2-linux-gnuspe > target as of r257975, so the change that affected this issue must have been > local to the rs6000 backend. Ok. so at the moment I'm going to claim that I am unable to recreate the initially reported problem in my environments, which are 64-bit or 64/32 mixed. Nothing pure 32-bit here, nothing e300* or e500*, etc. The ICe's that I did see (comment #4) seem to be to be a separate issue. Those only occur in my sandbox/debug build of gcc, which has CFLAGS,CXXFLAGS,CFLAGS_FOR_BUILD, CFLAGS_FOR_TARGET, etc all set to "-O0 -g3 -fno-inline". I otherwise don't see any ICE with this test case.
