From: Johannes Schindelin <hidden> Date: 2016-06-15 23:08:34
The pthread_exit() function is not expected to return. Ever.
Pointed out by Jeff King.
Signed-off-by: Johannes Schindelin <redacted>
---
compat/win32/pthread.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Jeff King <hidden> Date: 2016-06-15 23:08:34
On Tue, Mar 01, 2016 at 02:53:04PM +0100, Johannes Schindelin wrote:
quoted hunk
The pthread_exit() function is not expected to return. Ever.
Pointed out by Jeff King.
Signed-off-by: Johannes Schindelin <redacted>
---
compat/win32/pthread.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Johannes Schindelin <hidden> Date: 2016-06-15 23:08:34
Hi Peff,
On Tue, 1 Mar 2016, Jeff King wrote:
On Tue, Mar 01, 2016 at 02:53:04PM +0100, Johannes Schindelin wrote:
quoted
The pthread_exit() function is not expected to return. Ever.
Pointed out by Jeff King.
Signed-off-by: Johannes Schindelin <redacted>
---
compat/win32/pthread.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Looks obviously correct to me (I'll assume Windows isn't so crazy as to
let ExitThread ever return :) ).
Indeed, you are correct in your implicit assumption that I should have
clarified that in my commit message. I will amend the commit message.
Ciao,
Dscho
From: Johannes Schindelin <hidden> Date: 2016-06-15 23:08:34
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
Pointed out by Jeff King.
Signed-off-by: Johannes Schindelin <redacted>
---
Relative to v1, only the commit message changed (to clarify that
ExitThread() indeed never returns).
compat/win32/pthread.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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.":
Does this really mean that ExitThread() does not return ?
Just wondering...
quoted hunk
https://msdn.microsoft.com/en-us/library/windows/desktop/ms682659
Pointed out by Jeff King.
Signed-off-by: Johannes Schindelin <redacted>
---
Relative to v1, only the commit message changed (to clarify that
ExitThread() indeed never returns).
compat/win32/pthread.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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.
quoted hunk
Pointed out by Jeff King.
Signed-off-by: Johannes Schindelin <redacted>
---
Relative to v1, only the commit message changed (to clarify that
ExitThread() indeed never returns).
compat/win32/pthread.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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.
Your solution is pragmatic: NORETURN is defined in git-compat-util.h,
and by using it here, we depend on that pthread.h is included
sufficiently late that the macro is available at this point. The
instance in compat/nedmalloc/malloc.c.h is bracketed with #ifndef WIN32
so that it is not compiled on Windows, all other instances are after
git-compat-util.h or cache.h or in headers that are to be included only
after git-compat-util.h or cache.h per convention. Looks like we are safe.
From: Johannes Schindelin <hidden> Date: 2016-06-15 23:08:36
Hi,
On Tue, 1 Mar 2016, stefan.naewe@atlas-elektronik.com wrote:
Am 01.03.2016 um 15:13 schrieb Johannes Schindelin:
quoted
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.":
Does this really mean that ExitThread() does not return ?
From: Johannes Schindelin <hidden> Date: 2016-06-15 23:08:36
The pthread_exit() function is not expected to return. Ever. On Windows,
we call ExitThread() whose documentation claims: "Ends the calling
thread", i.e. there is no condition in which this function simply
returns: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682659
While at it, fix the return type to be void, as per
http://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_exit.html
Pointed out by Jeff King, helped by Stefan Naewe, Junio Hamano &
Johannes Sixt.
Signed-off-by: Johannes Schindelin <redacted>
---
compat/win32/pthread.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Interdiff vs v2:
diff --git a/compat/win32/pthread.h b/compat/win32/pthread.h
index 148db60..b6ed9e7 100644
--- a/compat/win32/pthread.h
+++ b/compat/win32/pthread.h
@@ -78,7 +78,7 @@ extern int win32_pthread_join(pthread_t *thread, void **value_ptr);
#define pthread_equal(t1, t2) ((t1).tid == (t2).tid)
extern pthread_t pthread_self(void);
-static inline int NORETURN pthread_exit(void *ret)
+static inline void NORETURN pthread_exit(void *ret)
{
ExitThread((DWORD)(intptr_t)ret);
}