https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80463
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Seems this doesn't ICE starting with r248863, so it likely just went latent. Maybe we should just error out on selective scheduling and explicit -fvar-tracking-assignments or -gstatement-frontiers, this scheduler really can't handle any debug insns well.
