This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] x86: Add __sigsetjmp_cancel and __setjmp_cancel
- From: Florian Weimer <fw at deneb dot enyo dot de>
- To: "H.J. Lu" <hjl dot tools at gmail dot com>
- Cc: Joseph Myers <joseph at codesourcery dot com>, "Carlos O'Donell" <carlos at redhat dot com>, "Tsimbalist\, Igor V" <igor dot v dot tsimbalist at intel dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Fri, 16 Mar 2018 09:24:38 +0100
- Subject: Re: [PATCH] x86: Add __sigsetjmp_cancel and __setjmp_cancel
- References: <CAMe9rOoB0t6CffwX-wgbBGNtaGgD923WoWmrtCjiXLc5pm=Z9g@mail.gmail.com> <alpine.DEB.2.20.1803151634160.26519@digraph.polyomino.org.uk> <CAMe9rOpLdFLbUE4NCH8L0C8CPMKtcMOepwhSr3PdpfnTgqHBqA@mail.gmail.com>
* H. J. Lu:
> +/* Function used in the macros. */
> +struct __jmp_buf_tag;
> +extern int __sigsetjmp_cancel (struct __jmp_buf_tag *__env, int __savemask)
> + __THROWNL __attribute_returns_twice__;
How is __THROWNL correct here? We do unwind through this function.
The __EXCEPTIONS guard is not effective because of LTO, and some
applications undefine __EXCEPTIONS to avoid the table-based
cancellation handlers.