public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
* [glibc] time: Fix compile error in itimer test affecting hurd
@ 2021-09-15 20:22 Stafford Horne
  0 siblings, 0 replies; only message in thread
From: Stafford Horne @ 2021-09-15 20:22 UTC (permalink / raw)
  To: glibc-cvs

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=5604830dea207bbd5fd5dbe087cc7ca30b527bb5

commit 5604830dea207bbd5fd5dbe087cc7ca30b527bb5
Author: Stafford Horne <shorne@gmail.com>
Date:   Thu Aug 19 23:47:07 2021 +0900

    time: Fix compile error in itimer test affecting hurd
    
    The recent change to use __KERNEL_OLD_TIMEVAL_MATCHES_TIMEVAL64 to avoid
    doing 64-bit checks on some platforms broke the test for hurd where
    __KERNEL_OLD_TIMEVAL_MATCHES_TIMEVAL64 is not defined.  With error:
    
        tst-itimer.c: In function 'do_test':
        tst-itimer.c:103:11: error: '__KERNEL_OLD_TIMEVAL_MATCHES_TIMEVAL64' undeclared (first use in this function)
          103 |       if (__KERNEL_OLD_TIMEVAL_MATCHES_TIMEVAL64)
              |           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        tst-itimer.c:103:11: note: each undeclared identifier is reported only once for each function it appears in
    
    Define a support helper to detect when setitimer and getitimer support
    64-bit time_t.
    
    Fixes commit 6e8a0aac2f ("time: Fix overflow itimer tests on 32-bit
    systems").
    
    Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>
    Cc: Joseph Myers <joseph@codesourcery.com>

Diff:
---
 support/support.h | 12 ++++++++++++
 time/tst-itimer.c |  5 +++--
 2 files changed, 15 insertions(+), 2 deletions(-)

diff --git a/support/support.h b/support/support.h
index c219e0d9d1..837a806531 100644
--- a/support/support.h
+++ b/support/support.h
@@ -152,6 +152,18 @@ static __inline bool support_path_support_time64 (const char *path)
 					    0x80000002ULL);
 }
 
+/* Return true if the setitimer and getitimer syscalls support 64-bit time_t
+   values without resulting in overflow.  This is not true on some linux systems
+   which have 64-bit time_t due to legacy kernel API's.  */
+static __inline bool support_itimer_support_time64 (void)
+{
+#ifdef __KERNEL_OLD_TIMEVAL_MATCHES_TIMEVAL64
+  return __KERNEL_OLD_TIMEVAL_MATCHES_TIMEVAL64;
+#else
+  return sizeof (__time_t) == 8;
+#endif
+}
+
 /* Return true if stat supports nanoseconds resolution.  PATH is used
    for tests and its ctime may change.  */
 extern bool support_stat_nanoseconds (const char *path);
diff --git a/time/tst-itimer.c b/time/tst-itimer.c
index bd7d7afe83..c6d623cb19 100644
--- a/time/tst-itimer.c
+++ b/time/tst-itimer.c
@@ -21,6 +21,7 @@
 #include <stdlib.h>
 #include <sys/time.h>
 #include <support/check.h>
+#include <support/support.h>
 #include <support/xsignal.h>
 #include <unistd.h>
 #include <time.h>
@@ -100,7 +101,7 @@ do_test (void)
 
       /* Linux does not provide 64 bit time_t support for getitimer and
 	 setitimer on architectures with 32 bit time_t support.  */
-      if (__KERNEL_OLD_TIMEVAL_MATCHES_TIMEVAL64)
+      if (support_itimer_support_time64())
 	{
 	  TEST_COMPARE (setitimer (timers[i], &it, NULL), 0);
 	  TEST_COMPARE (setitimer (timers[i], &(struct itimerval) { 0 },
@@ -131,7 +132,7 @@ do_test (void)
       it.it_interval.tv_usec = 20;
       it.it_value.tv_sec = 30;
       it.it_value.tv_usec = 40;
-      if (__KERNEL_OLD_TIMEVAL_MATCHES_TIMEVAL64)
+      if (support_itimer_support_time64())
 	{
 	  TEST_COMPARE (setitimer (timers[i], &it, NULL), 0);


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2021-09-15 20:22 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-09-15 20:22 [glibc] time: Fix compile error in itimer test affecting hurd Stafford Horne

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).