This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: What can a thread do with PTHREAD_STACK_MIN?
On 12/20/2017 10:18 AM, Adhemerval Zanella wrote:
> On 20/12/2017 15:30, Carlos O'Donell wrote:
>> So my position stands:
>>
>> (a) Make it very clear that PTHREAD_STACK_MIN is the minimum required to
>> start the thread, from now, going forwards.
>>
>> (b) Do our best to honour the relaxed semantics that allowed users to run
>> a few key functions in the past, this involves only getting back the
>> extra stack we lost to xsave.
>>
>> (c) Work to make it possible to use stack instrumentation and pthread_attr_setstacksize
>> to accurately reflect what the application is doing.
>>
>
> I think we also need document that thread cancellation requires some
> stack usage from libgcc for the stack unwinding, since it might not be
> obvious getting a stack overflow with pthread_cancel.
Agreed, we can add clarifications to pthread_create, pthread_join,
and pthread_cancel.
Does this mean you agree with (a) through (c)?
--
Cheers,
Carlos.