https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87836
--- Comment #15 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- > Regarding your suggestion, is there a way to get the compiler to reveal the > steps it goes through in compiling the program? All I get now is the > backtrace when it hits the error. I need to know what the compiler is doing > before that. You could break on execute_build_cfg and run the program until it is hit on the x86 and SPARC machines. Then add breakpoints on the various routines in the et-forest.c file and find out when the null pointer is created on SPARC.
