From: Joseph Myers <joseph@codesourcery.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Albert ARIBAUD <albert.aribaud@3adev.fr>, <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2 2/2] Y2038: make __tz_convert compatible with 64-bit-time
Date: Thu, 14 Jun 2018 19:40:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1806141938540.17828@digraph.polyomino.org.uk> (raw)
In-Reply-To: <29ea05e7-d4b0-876a-bf39-29ecf7bfa3da@cs.ucla.edu>
On Thu, 14 Jun 2018, Paul Eggert wrote:
> Also, isn't glibc a bit busted in this area? ctime_r is not part of standard
> C, so why isn't ctime_r treated like asctime_r, with a weak alias? Isn't this
> a (separate) bug that needs to be fixed, so that the resulting weak alias is
> like the one for localtime_r as far as 64-bit times is concerned?
localtime_r is defined in the same file as localtime, so needs to be weak.
ctime_r is not defined in the same file as ctime, and is not referenced by
the implementations of any standard C functions, so does not need to be
weak. (If it were referenced by a standard C function, the reference
would have to be to __ctime_r and ctime_r would have to be a weak alias of
that.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-06-14 19:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 13:51 [PATCH v2 0/2] Y2038 support batch 1 - __time64_t and __tz_convert Albert ARIBAUD (3ADEV)
2018-06-14 13:51 ` [PATCH v2 2/2] Y2038: make __tz_convert compatible with 64-bit-time Albert ARIBAUD (3ADEV)
2018-06-14 17:07 ` Paul Eggert
2018-06-14 17:52 ` Albert ARIBAUD
2018-06-14 18:52 ` Paul Eggert
2018-06-14 19:40 ` Joseph Myers [this message]
2018-06-16 14:03 ` Albert ARIBAUD
2018-06-16 14:23 ` Paul Eggert
2018-06-16 18:21 ` Albert ARIBAUD
2018-06-14 13:51 ` [PATCH v2 1/2] Y2038: Add 64-bit time for all architectures Albert ARIBAUD (3ADEV)
2018-06-14 13:57 ` Joseph Myers
2018-06-14 18:51 ` Albert ARIBAUD
2018-06-14 16:56 ` Paul Eggert
2018-06-14 17:52 ` Albert ARIBAUD
2018-07-30 5:38 ` Ben Hutchings
2018-07-30 5:41 ` Ben Hutchings
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.1806141938540.17828@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=albert.aribaud@3adev.fr \
--cc=eggert@cs.ucla.edu \
--cc=libc-alpha@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).