public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Wolfram Gloger <wmglo@dent.med.uni-muenchen.de>
Cc: libc-hacker@sources.redhat.com
Subject: Re: [PATCH] Fix linuxthreads with pthread_attr_setstack{,addr}
Date: Sat, 01 May 2004 09:38:00 -0000	[thread overview]
Message-ID: <20040501072454.GA5191@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <20040430180417.2588.qmail@md.dent.med.uni-muenchen.de>

On Fri, Apr 30, 2004 at 06:04:17PM -0000, Wolfram Gloger wrote:
> Hi,
> 
> > It is in pthread_join's RATIONALE:
> > http://www.opengroup.org/onlinepubs/009695399/functions/pthread_join.html
> 
> Interesting.  AFAIC remember, this has changed from when I looked at
> it in 2001.  Although only in the "informative" section, I would
> actually welcome such a guarantee, and think we should make it
> possible to free application stacks after a return from
> pthread_join().

Actually, the yesterday released TC2 clarifies user defined stacks
and indeed a conforming application cannot free ever user defined stack
once it has been used successfully in some pthread_create or SIGEV_THREAD
notification. 2.9.8 is new in TC2:
http://www.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_09.html#tag_02_09_08

	Jakub

  reply	other threads:[~2004-05-01  9:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-29 16:31 Jakub Jelinek
2004-04-29 16:43 ` Jakub Jelinek
2004-04-30 17:14   ` Wolfram Gloger
2004-04-30 17:33     ` Jakub Jelinek
2004-04-30 18:04       ` Wolfram Gloger
2004-05-01  9:38         ` Jakub Jelinek [this message]
2004-05-03 21:12 ` Ulrich Drepper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040501072454.GA5191@sunsite.ms.mff.cuni.cz \
    --to=jakub@redhat.com \
    --cc=libc-hacker@sources.redhat.com \
    --cc=wmglo@dent.med.uni-muenchen.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).