https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103510
--- Comment #5 from ashimida ---
(In reply to Andrew Pinski from comment #3)
> The only registers which are saved are the callee saved register IIRC. So
> you need to know the ABI.
Hi Andrew,
Is it reasonable to save all registers (include cal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103510
--- Comment #4 from ashimida ---
(In reply to Andrew Pinski from comment #3)
> The only registers which are saved are the callee saved register IIRC. So
> you need to know the ABI.
Thanks Andrew,
I saw the following description in the IA-64 C+
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103510
--- Comment #3 from Andrew Pinski ---
The only registers which are saved are the callee saved register IIRC. So you
need to know the ABI.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103510
--- Comment #2 from Andrew Pinski ---
Funny there is a comment in the libgcc sources:
/* This will segfault if the register hasn't been saved. */
Which has been there since day 1 of IA-64 ABI exception handling back in
g:52a11cbfcf0cfb32628b6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103510
--- Comment #1 from ashimida ---
For example, such a c code works find in clang with libunwind,
and will cause a crash in gcc with libgcc in aarch64.
#include
#include
#include
_Unwind_Reason_Code callback(struct _Unwind_Context *context, v
