https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55212
--- Comment #361 from Oleg Endo <olegendo at gcc dot gnu.org> --- (In reply to Kazumoto Kojima from comment #360) > > I think that it's an issue for call insns not for normal insns. As reported > in c#276, LRA handles call insns specially, and it seems to be an argument > about that process. It's not directly related to our sfunc issue. OK, thanks for checking it. Do you know if there's any particular reason why sfunc on SH can't be done via regular call insn path? I can imagine it was originally done to optimize the number/types of regs used/clobbered by the sfunc libcall. Now I'm wondering if the same could be achieved using the regular call insn path ... (to better follow LRA's assumptions)
