public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
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 1/2] Y2038: add type __time64_t
Date: Wed, 13 Jun 2018 16:39:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.20.1806131635320.28522@digraph.polyomino.org.uk> (raw)
In-Reply-To: <c749dc84-72c4-3618-2f51-8a6790baab00@cs.ucla.edu>

On Wed, 13 Jun 2018, Paul Eggert wrote:

> Albert ARIBAUD wrote:
> > - a "size" macro (e.g. __TIMESIZE) defined equal to __WORDSIZE except
> >    for x32 where it would be defined as 64?
> > 
> > I have a slight preference for the "size" form.
> 
> Works for me. Though C11 uses _WIDTH for names that count bit widths of
> integers, so I'd mildly prefer __TIME_WIDTH as it is a new name.

Whatever the name, it needs to be clear that this macro relates to the 
time_t used by default (unsuffixed) functions in this glibc - *not* 
necessarily the time_t for the current compilation.  (Rather, _TIME_BITS 
== 64 && (new macro) == 32 would be the condition for the installed 
headers to need to redirect calls to time-related functions.)

The width macros are from TS 18661-1, not C11 (hopefully they'll end up as 
an unconditional feature of C2x without requiring 
__STDC_WANT_IEC_60559_BFP_EXT__, since there is demand for them outside 
the floating-point context of passing them to the fromfp functions).  If 
there were a TIME_WIDTH addition to that set of macros, I'd expect it to 
relate to the current compilation.

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2018-06-13 16:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-13  7:00 [PATCH 0/2] Y2038 support batch 1 - __time64_t and __tz_convert Albert ARIBAUD (3ADEV)
2018-06-13  7:00 ` [PATCH 2/2] Y2038: make __tz_convert compatible with 64-bit-time Albert ARIBAUD (3ADEV)
2018-06-13  9:10   ` Florian Weimer
2018-06-13  9:37     ` Albert ARIBAUD
2018-06-13  9:40       ` Florian Weimer
2018-06-13 10:21         ` Albert ARIBAUD
2018-06-13 10:55           ` Albert ARIBAUD
2018-06-13 13:08           ` Florian Weimer
2018-06-13 14:29             ` Joseph Myers
2018-06-13 14:24         ` Joseph Myers
2018-06-18 13:34           ` Florian Weimer
2018-06-13  9:11   ` Paul Eggert
2018-06-13  9:14     ` Florian Weimer
2018-06-13  9:30       ` Albert ARIBAUD
2018-06-13 14:22     ` Joseph Myers
2018-06-13 14:18   ` Joseph Myers
2018-06-13  7:00 ` [PATCH 1/2] Y2038: add type __time64_t Albert ARIBAUD (3ADEV)
2018-06-13  8:38   ` Paul Eggert
2018-06-13 12:36     ` Albert ARIBAUD
2018-06-13 14:13   ` Joseph Myers
2018-06-13 16:19     ` Albert ARIBAUD
2018-06-13 16:35       ` Paul Eggert
2018-06-13 16:39         ` Joseph Myers [this message]
2018-06-13 18:46           ` Paul Eggert
2018-06-13  7:59 ` [PATCH 0/2] Y2038 support batch 1 - __time64_t and __tz_convert Albert ARIBAUD
2018-06-13 14:08   ` Joseph Myers
2018-06-13 15:38     ` Albert ARIBAUD

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