From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/409 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: cluts daily reports 8/12 - continuing pthread_eintr, still stuck with alloc Date: Fri, 12 Aug 2011 11:39:34 -0400 Message-ID: <20110812153934.GI132@brightrain.aerifal.cx> References: <4E4493E6.6050809@gmail.com> <20110812024151.GF132@brightrain.aerifal.cx> <4E45496A.3010505@gmail.com> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: dough.gmane.org 1313164376 10099 80.91.229.12 (12 Aug 2011 15:52:56 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 12 Aug 2011 15:52:56 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-410-gllmg-musl=m.gmane.org@lists.openwall.com Fri Aug 12 17:52:52 2011 Return-path: Envelope-to: gllmg-musl@lo.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by lo.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1Qru2Q-0003x7-MS for gllmg-musl@lo.gmane.org; Fri, 12 Aug 2011 17:52:46 +0200 Original-Received: (qmail 17863 invoked by uid 550); 12 Aug 2011 15:52:46 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 17855 invoked from network); 12 Aug 2011 15:52:46 -0000 Content-Disposition: inline In-Reply-To: <4E45496A.3010505@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:409 Archived-At: On Fri, Aug 12, 2011 at 05:40:26PM +0200, Luka Marčetić wrote: > >>Both musl and glibc macros generate invalid code for this one, it > >>ends with `do {;` in both cases iirc. Strange - what is it? > >You might want to read this: > >http://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_cleanup_pop.html > > > >There's even a sample implementation in the rationale. > > > >Rich > > What I read was: > > "The thread exits (that is, calls/pthread_exit/() )." > > Then I clicked the link(http://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_exit.html ), > hoping to find this: > > "An implicit call to/pthread_exit/() is made when a thread other > than the thread in which/main/() was first invoked returns from the > start routine that was used to create it." > > And when I did, I've overlooked '{', expecting an '}'. I regard this > as slight inconsistency in the standard. At least it's missing the > word "explicitly", but I'd reword it altogether hehe. > Anyway, I'll just cast the void* to a function pointer and call it directly. I don't follow what you're saying in this email... Rich