https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96061
--- Comment #7 from H.J. Lu <hjl.tools at gmail dot com> --- (In reply to Alexander Popov from comment #6) > >> Could you explain the connection between your attribute for zeroing > >> registers and 'no_caller_saved_registers' attribute? > > > > We are porting > > > > https://gitlab.com/x86-gcc/gcc/-/tree/users/hjl/caller-saved/old > > > > from x86 back-end to middle-end. no_caller_saved_registers changes what > > registers zero_call_used_regs can do. Move no_caller_saved_registers to > > middle-end has a direct impact on zero_call_used_regs implementation in > > middle-end. > > Ok. So, as I can understand, your work will enable > 'no_caller_saved_registers' attribute for all architectures. Am I right? No. We are implementing zero_call_used_regs in middle-end. Someone can piggyback no_caller_saved_registers on our work.
