https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105551
--- Comment #2 from rguenther at suse dot de <rguenther at suse dot de> --- On Tue, 10 May 2022, burnus at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105551 > > Tobias Burnus <burnus at gcc dot gnu.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Target Milestone|--- |13.0 > Summary|[nvptx] ICE in |[13 Regression] [nvptx] ICE > |final_scan_insn_1, at |in final_scan_insn_1, at > |final.cc:2629 when building |final.cc:2629 when building > |libgcc2.c since |libgcc2.c since > |r13-259-g76db543db88727789a |r13-259-g76db543db88727789a > |6c117608a23edc2eace713 |6c117608a23edc2eace713 > > --- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> --- > Glancing at the current patch, it seems as if the > > || debug_hooks->var_location == do_nothing_debug_hooks.var_location) > > check got lost. Yes, there's no way to check it at this point since the debug hooks are not yet set up. I wonder whether this would be better done in the var-tracking gate then? Or where exactly does the failure materialize? I suppose since we check for dwarf_debuginfo_p () we could also simply look at dwarf2_debug_hooks.var_location but then that _always_ is dwarf2out_var_location, so maybe I'm missing something...
