https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124907
--- Comment #2 from Drea Pinski <pinskia at gcc dot gnu.org> --- (In reply to Christoph Müllner from comment #1) > The underlying issue seems to be that dwarf2cfi assumes every path entering >no the same code region has the same set of currently saved/restored registers, > but separate shrink-wrapping can violate that assumption: > * shrink-wrap can place save/restore code on only some CFG paths > * when those paths later merge, one predecessor can arrive with a register > still marked as saved, while another arrives with it restored > * in this bug, that happened for AArch64 FP callee-save v15 > * dwarf2cfi treated that difference as impossible and aborted in > maybe_record_trace_start > > I believe this affects other architectures as well. Oh no. That is wrong.
