public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Adhemerval Zanella <azanella@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc/azanella/y2038] y2038: Add __USE_TIME_BITS64 support for struct timeval Date: Mon, 1 Mar 2021 17:37:49 +0000 (GMT) [thread overview] Message-ID: <20210301173749.582BD393A404@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=cee329fc01161376263a5f65ba36b74cc3a67c05 commit cee329fc01161376263a5f65ba36b74cc3a67c05 Author: Adhemerval Zanella <adhemerval.zanella@linaro.org> Date: Wed Feb 17 16:19:23 2021 -0300 y2038: Add __USE_TIME_BITS64 support for struct timeval The __USE_TIME_BITS64 is not defined internally yet. Diff: --- time/bits/types/struct_timeval.h | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/time/bits/types/struct_timeval.h b/time/bits/types/struct_timeval.h index 70394ce886..3466137c35 100644 --- a/time/bits/types/struct_timeval.h +++ b/time/bits/types/struct_timeval.h @@ -7,7 +7,12 @@ microsecond but also has a range of years. */ struct timeval { +#ifdef __USE_TIME_BITS64 + __time64_t tv_sec; /* Seconds. */ + __suseconds64_t tv_usec; /* Microseconds. */ +#else __time_t tv_sec; /* Seconds. */ __suseconds_t tv_usec; /* Microseconds. */ +#endif }; #endif
next reply other threads:[~2021-03-01 17:37 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-01 17:37 Adhemerval Zanella [this message] -- strict thread matches above, loose matches on Subject: below -- 2021-06-08 20:48 Adhemerval Zanella 2021-05-26 16:24 Adhemerval Zanella 2021-03-05 19:20 Adhemerval Zanella 2021-03-04 17:38 Adhemerval Zanella 2021-03-04 11:31 Adhemerval Zanella 2021-03-02 12:33 Adhemerval Zanella 2021-02-26 20:42 Adhemerval Zanella 2021-02-23 20:40 Adhemerval Zanella 2021-02-23 12:38 Adhemerval Zanella
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=20210301173749.582BD393A404@sourceware.org \ --to=azanella@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: linkBe 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).