From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Johannes Sixt" <j6t@kdbg.org>,
git@vger.kernel.org, "Jeff King" <peff@peff.net>,
"Torsten Bögershausen" <tboegi@web.de>
Subject: Re: [PATCH v2] Mark win32's pthread_exit() as NORETURN
Date: Wed, 2 Mar 2016 20:10:29 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1603022008240.3152@virtualbox> (raw)
In-Reply-To: <xmqqio166l0n.fsf@gitster.mtv.corp.google.com>
Hi,
On Tue, 1 Mar 2016, Junio C Hamano wrote:
> Johannes Sixt <j6t@kdbg.org> writes:
>
> > Am 01.03.2016 um 15:13 schrieb Johannes Schindelin:
> >> The pthread_exit() function is not expected to return. Ever. On Windows,
> >> we call ExitThread() whose documentation claims: "This function does not
> >> return a value.":
> >>
> >> https://msdn.microsoft.com/en-us/library/windows/desktop/ms682659
> >
> > This is misleading: MSDN marks all functions declared void as "does
> > not return a value," for example, look at EnterCriticalSection:
> >
> > https://msdn.microsoft.com/en-us/library/windows/desktop/ms682608
> >
> > For this reason, I actually prefer your version 1 patch without the
> > explanation.
>
> ;-)
Well, I really like to have that link so I can find it very easily myself
by simply inspecting the Git log. And the explanation itself was easily
fixed.
>
> >> -static inline int pthread_exit(void *ret)
> >> +static inline int NORETURN pthread_exit(void *ret)
> >
> > I would have written it as
> >
> > #ifdef __GNUC__
> > __attribute__((__noreturn__))
> > #endif
> > static inline int pthread_exit(void *ret) ...
> >
> > but I can live with your version as long as it compiles.
>
> Either way, let's make sure that the final version returns "void",
> cf.
>
> http://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_exit.html
Fixed, too, in the upcoming v3.
Ciao,
Dscho
next prev parent reply other threads:[~2016-03-02 19:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 13:53 [PATCH] Mark win32's pthread_exit() as NORETURN Johannes Schindelin
2016-03-01 13:57 ` Jeff King
2016-03-01 14:11 ` Johannes Schindelin
2016-03-01 14:13 ` [PATCH v2] " Johannes Schindelin
2016-03-01 14:38 ` stefan.naewe
2016-03-01 17:57 ` Junio C Hamano
2016-03-02 19:11 ` Johannes Schindelin
2016-03-01 19:34 ` Johannes Sixt
2016-03-01 19:44 ` Junio C Hamano
2016-03-02 19:10 ` Johannes Schindelin [this message]
2016-03-02 19:11 ` [PATCH v3] " Johannes Schindelin
2016-03-02 20:33 ` Junio C Hamano
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=alpine.DEB.2.20.1603022008240.3152@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=peff@peff.net \
--cc=tboegi@web.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 NNTP newsgroup(s).