https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84342
Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ramana at gcc dot gnu.org
--- Comment #11 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #10)
> GCC 8.1 has been released.
(In reply to Jeffrey A. Law from comment #9)
> Alex: I realize that's the point of the hook. But I'm pretty sure there's
> no way to fix the ARM port given the point at which lengths are set and the
> point at which ccfsm is valid are at two different times. We'd either need
> a revamp of ccfsm or some layering violations to allow dwarf2out to access
> the underlying routines for length query and bypass the cache.
>
> It's my view this BZ is resolved. But if you want to keep it open to track
> the incorrect lengths in the ARM port, that's fine. But it's certainly no
> longer a regression for gcc-8.
In which case should this still retain the P1 status ?
The builds are ok since Alex's patch and we need to look at this at some point
of time.
Richard E and I have been talking about whether ccfsm actually makes sense in
2018 and whether we should just rip it out anyway and make sure that the rtl
optimizers get it right rather than carry this in the far future. It's only
used in A32 state, it's probably not got a huge amount going for it and maybe
we should just rip it out.
