https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106943
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|wrong-code |ice-on-valid-code
--- Comment #23 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Alexander Monakov from comment #6)
> I'm giving this a shot, and with -flto-partition=1to1 there's a ranger ICE
> (below).
>
> 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?
The easiest way to debug this kind of ICE is first get a reduced testcase.
1) Generate all of the preprocessed sources
2) Write a simple script which does the following:
** Remove the old object files
** compile the (already generated) preprocessed sources with -flto
** compile (link) the object files with the -r option and what ever options
** check if the ICE was there
3) Find the min number of preprocessed sources required to reproduce the issue
4) then reduce the remaining sources (either using delta or cvise or what ever
tool you want to use)
Hope this helps.
