This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
With a stack adjustment in the call delay slot, the unwinder will be 4-bytes off the correct adjustment when crossing that frame; this probably is an issue of how program counters map to FDEs (< vs<=).
CCing Richard Henderson here, who's probably the one to answer this. Richard, I remember seeing related discussion in the archives on this issue, as well as comments in the current GCC dwarf2cfi.c:scan_trace() code, can you confirm?
FWIW, pushing the unwind data from the delay slot to before the call is exactly what gcc itself does. Though, really, we try very hard to *not* place unwind-related insn in delay slots.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |