https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87015
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
If what you are compiling has multiple sources and if e.g. -O0 helps, then you
could bisect among the object files to find the problematic *.o file.
That can be then preprocessed e.g. with -save-temps.
Further analysis can be done by using bisection in the file using #pragma GCC
optimize (0) and/or __attribute__((optimize (0))) to find problematic
function/method.
