https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106943
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org
--- Comment #13 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
> What's the current best practice for LTO debugging? I don't imagine there's
> an > easy way to identify which of 2000 lto1 invocation crashes, or attach
> gdb to it? Or at least generate a corefile
What I do is to compile with --save-temps --verbose and then one can see which
ltrans ICEd in error message from internal make. The dump also contains all of
ltrans command lines (sometimes garbled by parallel output unoless you are
willing to wait for -flto=1). Invoke the corresponding ltrnans command line
from gdb and wait for crash.
Indeed it is quite long time problem with clang not building with lifetime DSE
and strict aliasing. I wonder why this is not fixed on clang side?
