This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH 2/4] aarch64: Re-implement setcontext without sigreturn syscall
- From: Richard Henderson <rth at twiddle dot net>
- To: Rich Felker <dalias at aerifal dot cx>, Will Newton <will dot newton at linaro dot org>
- Cc: libc-alpha <libc-alpha at sourceware dot org>
- Date: Wed, 19 Mar 2014 10:43:55 -0700
- Subject: Re: [PATCH 2/4] aarch64: Re-implement setcontext without sigreturn syscall
- Authentication-results: sourceware.org; auth=none
- References: <1394707543-9690-1-git-send-email-will dot newton at linaro dot org> <1394707543-9690-2-git-send-email-will dot newton at linaro dot org> <20140319171245 dot GU26358 at brightrain dot aerifal dot cx> <CANu=Dmix9Wdt2DFuPrDR-KiSXV+mv9gw3-6qupcXGRi9FKFbXQ at mail dot gmail dot com> <20140319173741 dot GV26358 at brightrain dot aerifal dot cx>
On 03/19/2014 10:37 AM, Rich Felker wrote:
> On Wed, Mar 19, 2014 at 05:19:23PM +0000, Will Newton wrote:
>> But on the other hand sigreturn interacts badly with sigaltstack which
>> actually causes problems with real running code (in this case the Go
>> language).
>
> Could you explain the bad interaction? I'd be interested in knowing
> what it is (since I was planning on using sigreturn to implement the
> ucontext functions in musl) and if I knew, I might even have a
> workaround.
Yes, please explain. I've used sigreturn on alpha since day 1 and
haven't noticed a problem.
r~