unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Zack Weinberg <zackw@panix.com>, Wolfgang Denk <wd@denx.de>,
	GNU C Library <libc-alpha@sourceware.org>,
	Alistair Francis <alistair.francis@wdc.com>,
	Alistair Francis <alistair23@gmail.com>
Subject: Re: Accelerating Y2038 glibc fixes
Date: Tue, 30 Jul 2019 13:02:49 +0200	[thread overview]
Message-ID: <20190730130249.00e1ffaa@jawa> (raw)
In-Reply-To: <alpine.DEB.2.21.1907292001060.1468@digraph.polyomino.org.uk>

[-- Attachment #1: Type: text/plain, Size: 2339 bytes --]

Hi Joseph, Zack,

> On Mon, 29 Jul 2019, Zack Weinberg wrote:
> 
> > I’m prepared to work with you to come up with better wording but I
> > need to ask you a bunch of questions.  Could you please reply to
> > each of the queries marked Qn below?  
> 
> Note that while these cases are things we should think about in
> working out (for example) what the best semantics for
> __ASSUME_TIME64_SYSCALLS are, they shouldn't be part of how it's
> defined (a definition that says this is what happens in each of five
> cases is not a cleanly defined interface); the definition should
> rather be such that readers can see what the answer would be for each
> of those cases - and for any other cases that may arise in future.
> (I think the current definition is that it means either a specified
> set of suffixed syscalls using 64-bit time are guaranteed to be
> available at runtime, *or* that the corresponding unsuffixed syscalls
> use 64-bit time and are guaranteed to be available, so that #define
> of the suffixed names to the unsuffixed ones is OK in that case.)
> 

The above definition is the concise description of
__ASSUME_TIME64_SYSCALLS.

> There is at least one case you didn't list (or a variant of case 5
> that's different as far as glibc's concerned but not as far as the
> kernel's concerned): new glibc ports for ILP32 ABIs where the oldest
> kernel version supported is older than 5.1, should we wish for any
> such port to support only 64-bit time and not 32-bit time (so
> __TIMESIZE == 64, __WORDSIZE == 64, __SYSCALL_WORDSIZE == 64) - and
                    ^^^^^^^^^^^^^^^^ - shouldn't be WORDSIZE == 32 ?

> once we have the support in glibc to make it possible not to support
> 32-bit time in such a case, it seems a good idea for any such new
> ports to use it.
> 
> __WORDSIZE is the size, in bits, of "long int".  __SYSCALL_WORDSIZE
> (when defined) is the size, in bits, of __syscall_slong_t (the "long
> int" type in the syscall interface, which is the same as userspace
> "long int" except for x32).
> 


Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-07-30 11:03 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12  7:21 Accelerating Y2038 glibc fixes Wolfgang Denk
2019-07-16  9:32 ` Wolfgang Denk
2019-07-16 11:50 ` Siddhesh Poyarekar
2019-07-16 12:40   ` Wolfgang Denk
2019-07-16 12:44 ` Florian Weimer
2019-07-16 14:52   ` Wolfgang Denk
2019-07-16 15:09     ` Florian Weimer
2019-07-16 15:19       ` Andrew Pinski
2019-07-17 14:15     ` Arnd Bergmann
2019-07-17 14:41       ` Florian Weimer
2019-07-17 16:00         ` Wolfgang Denk
2019-07-17 16:04           ` Florian Weimer
2019-07-17 16:18             ` Lukasz Majewski
2019-07-18 18:53               ` Adhemerval Zanella
2019-07-18 19:13                 ` Florian Weimer
2019-07-18 20:31                   ` Adhemerval Zanella
2019-07-18 21:20                     ` Florian Weimer
2019-07-18 22:32                     ` Paul Eggert
2019-07-19  7:21                       ` Andreas Schwab
2019-07-19  3:06                     ` Rich Felker
2019-07-19 17:44                       ` Adhemerval Zanella
2019-07-19 19:03                         ` Alistair Francis
2019-07-25 20:40                 ` Joseph Myers
2019-07-29 17:47                   ` Adhemerval Zanella
2019-07-29 19:58                     ` Joseph Myers
2019-07-29 21:00                       ` Adhemerval Zanella
2019-07-29 21:08                         ` Joseph Myers
2019-07-29 23:12                           ` Paul Eggert
2019-07-29 23:30                             ` Joseph Myers
2019-07-17 17:50       ` Rich Felker
2019-07-17 21:57         ` Lukasz Majewski
2019-07-17 22:37           ` Rich Felker
2019-07-18  7:20             ` Lukasz Majewski
2019-07-18 13:35               ` Rich Felker
2019-07-18 14:47           ` Rich Felker
2019-07-18 14:49             ` Florian Weimer
2019-07-18 15:46               ` Rich Felker
2019-07-18 16:43                 ` Adhemerval Zanella
2019-07-20  4:43             ` Rich Felker
2019-07-25 19:54 ` Joseph Myers
2019-07-26 10:39   ` Lukasz Majewski
2019-07-29 18:55     ` Zack Weinberg
2019-07-29 20:12       ` Joseph Myers
2019-07-30 11:02         ` Lukasz Majewski [this message]
2019-07-30 12:24           ` Joseph Myers
2019-07-30 14:04       ` Lukasz Majewski
2019-08-09  7:25         ` Lukasz Majewski
     [not found]           ` <CAKCAbMhOMQ9yTFpy+OQkDvZPPFf_fFn6oSxjvLTaUwC4jpPRag@mail.gmail.com>
2019-08-09 12:32             ` Fwd: " Zack Weinberg
2019-07-30 19:58       ` Joseph Myers
2019-07-30 20:28         ` Florian Weimer

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190730130249.00e1ffaa@jawa \
    --to=lukma@denx.de \
    --cc=alistair.francis@wdc.com \
    --cc=alistair23@gmail.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=wd@denx.de \
    --cc=zackw@panix.com \
    /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).