https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102622
--- Comment #8 from Aldy Hernandez <aldyh at gcc dot gnu.org> --- (In reply to H.J. Lu from comment #6) > (In reply to Aldy Hernandez from comment #4) > > Can you try with -fno-thread-jumps to make sure its really the threader at > > play? > > -fno-thread-jumps fixes the bug. > > > If so, you could try to narrow it down to the problematic threading path > > with: > > > > -fdbg-cnt=registered_jump_thread:N:N > > > > where N is the number that causes the problem. > > What N should I try? I got > > [hjl@gnu-skx-1 gcc]$ ./xgcc -B./ -S -O3 -march=native > /export/project/git/gcc-bisect/pr102622.cc > -fdbg-cnt=registered_jump_thread:10:10 > cc1plus: error: Interval overlap of ??-fdbg-cnt=registered_jump_thread??: > [1, 10] and [1, 10] Sorry, that should've been N-N for the Nth attempt. Or M-N for attempts M through N. -fdbg-cnt is annoying in that it doesn't give much feedback.
