* Vineet Gupta: > On 12/20/18 4:40 AM, Florian Weimer wrote: >> * Adhemerval Zanella: >> >>> The only advantage of using a larger sigset_t from glibc standpoint is if >>> kernel ever change it maximum number of supported signals it would not be >>> a ABI change (it would be if glibc provided sigset_t need to be extended). >> It's not just the kernel. We might want to restore additional state in >> sigsetjmp, and historically, the excess signal space in sigset_t has >> provided a way to do that even if there is no other space left in the >> jump buffer. > > And that additional state is architectural state (more FPU regs etc > etc) or something libc generic. On both counts, that doesn't sound > like a clean interface design ! Sure, setjmp/longjmp is quite horrible as an interface, considering that register files do evolve. But it's what we have in C, and it's good to have at least some extension space there (but it could be expressed in a better way, definitely). Thanks, Florian _______________________________________________ linux-snps-arc mailing list linux-snps-arc@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/linux-snps-arc
