This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
David Mosberger wrote: > If there are no objections, please apply this patch. I don't like this. The behavior of longjmp if the starting point is using the alternate stack while the destination uses the normal stack, is currently unspecified in POSIX. I've asked for clarification in the POSIX working group. The result I expect is "don't do it", aka, unspecified. So, this is no case the normal setjmp/longjmp needs to handle. For the unwind/cancellation handling this might not apply. But it is an implementation decision to use setjmp/longjmp. So, the solution should be to use special versions of those interfaces in the nptl implementation. For all platforms but ia64 the new names are just aliases of the normal code. For ia64 this heavier code is used. This will also take care of most of the performance penalties since they don't apply in general, only in the thread code. -- â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |