https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89093
--- Comment #36 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #35)
> (In reply to Bernd Edlinger from comment #33)
> > (In reply to Ramana Radhakrishnan from comment #32)
> > >
> > > Either I drop the warning or I keep the hunk in eh_personality.cc - any
> > > preferences / thoughts ?
> >
> > It would feel safer, if only the functions that need it
> > had a target attribute like:
> >
> > _Unwind_Reason_Code
> > #ifdef __ARM_EABI_UNWINDER__
> > __attribute__((target("general-regs-only")))
> > PERSONALITY_FUNCTION (_Unwind_State state,
> > struct _Unwind_Exception* ue_header,
> > struct _Unwind_Context* context)
>
> Agreed - will this work instead?
Aren't there many functions that are inlined into it (then it would be fine)
but could not be inlined (and then it would be a problem, at least in theory)?
Though, if there are inlines that are used in other TUs and those TUs are not
general-regs-only and we decide not to inline, then it might be pure luck if
COMDAT is won bu eh-personality.o versions or some other ones.
