https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83758
--- Comment #23 from acsawdey at gcc dot gnu.org ---
(In reply to Alexandre Oliva from comment #19)
> I was copied, presumably because the problem occurred in var-tracking.
>
> I've tried to duplicate the problem on gcc112. I bootstrapped the trunk
> (without any --with-cpu flag), and then build attachment 43208 [details]
> with stage3:
>
> $ ./gccgo -B./ -I../../libgo/go -I../powerpc64le-unknown-linux-gnu/libgo
> -I../powerpc64le-unknown-linux-gnu/libgo/go -O2 -g t.go -mcpu=power8 -c
> [success]
>
> Given this, I conclude that the problem only occurs if the compiler is
> bootstrapped --with-cpu=power[89]. This suggests to me that, although the
> ICE is triggered in var-tracking, the problem is unlikely to be there: the
> compiler is getting miscompiled. I suppose that, by now, you already knew
> that ;-)
Alexandre,
gcc112 has glibc 2.17, which is the same as the machine willow2 I was testing
on here and I have verified that split-stack is always disabled if you build
gcc against that glibc. Since the problem apparently requires split-stack, the
problem will not occur under these conditions.
What you can try is building on gcc112 using /opt/at10.0/bin/gcc because AT10
toolchain includes glibc 2.24 so it should reproduce with that.
Thanks,
Aaron
