public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] y2038: hurd: Provide __clock_gettime64 function
Date: Tue,  5 May 2020 22:57:42 +0000 (GMT)	[thread overview]
Message-ID: <20200505225742.ECA893890C0A@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=1959ed4b9e9f95c991abdf31b24fb8cdf98475e2

commit 1959ed4b9e9f95c991abdf31b24fb8cdf98475e2
Author: Lukasz Majewski <lukma@denx.de>
Date:   Thu Jan 16 14:27:27 2020 +0100

    y2038: hurd: Provide __clock_gettime64 function
    
    For Linux glibc ports the __TIMESIZE == 64 ensures proper aliasing for
    __clock_gettime64 (to __clock_gettime).
    When __TIMESIZE != 64 (like ARM32, PPC) the glibc expects separate definition
    of the __clock_gettime64.
    
    The HURD port only provides __clock_gettime, so this patch adds
    __clock_gettime64 as a tiny wrapper on it.
    Acked-by: Samuel Thibault <samuel.thibault@ens-lyon.org>

Diff:
---
 sysdeps/mach/clock_gettime.c | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/sysdeps/mach/clock_gettime.c b/sysdeps/mach/clock_gettime.c
index ac3547df3c..fbd80536d5 100644
--- a/sysdeps/mach/clock_gettime.c
+++ b/sysdeps/mach/clock_gettime.c
@@ -49,3 +49,17 @@ versioned_symbol (libc, __clock_gettime, clock_gettime, GLIBC_2_17);
 strong_alias (__clock_gettime, __clock_gettime_2);
 compat_symbol (libc, __clock_gettime_2, clock_gettime, GLIBC_2_2);
 #endif
+
+int
+__clock_gettime64 (clockid_t clock_id, struct __timespec64 *ts64)
+{
+  struct timespec ts;
+  int ret;
+
+  ret = __clock_gettime (clock_id, &ts);
+  if (ret == 0)
+    *ts64 = valid_timespec_to_timespec64 (ts);
+
+  return ret;
+}
+libc_hidden_def (__clock_gettime64)


                 reply	other threads:[~2020-05-05 22:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200505225742.ECA893890C0A@sourceware.org \
    --to=lukma@sourceware.org \
    --cc=glibc-cvs@sourceware.org \
    /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).