From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-3.9 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_EF,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 8CDD31F462 for ; Tue, 30 Jul 2019 11:03:07 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type; q=dns; s=default; b=VwHeK HDWLGwnwf3XIDs9K0LR9iwAaphnr9vjA9mBINQTePWRj053A4QWKSACBDX+ZHUEP 2CmwTrbqLWZ3YvytWPZyx5Z4e56XwOuLcItBq5gdZptvKEjmrG3Vjo/eKdfh6mBy cpn0qC4kXyLkFaNcvDHrRt8e7VTw85ZGGklVwA= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type; s=default; bh=C6WKjZCLgOz PsG4YJtfLiEz/osg=; b=J8LCRDor+UEjb4jw1sDMaq1y3bKntUxTbCHxCyQLJ05 1srNV40DPBO47ZiDgabhSxIlll9gyiLi0PrsSd1orHGoN2ZAaISOdWnr2z3JJCUz EetX5hqFm3jSKaRkWD3hXoqhpxUWt93GbF+L3WEDaAKUpVeRJxgsorD0a+ZY3fVE = Received: (qmail 16621 invoked by alias); 30 Jul 2019 11:03:04 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 16597 invoked by uid 89); 30 Jul 2019 11:03:03 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: mail-out.m-online.net Date: Tue, 30 Jul 2019 13:02:49 +0200 From: Lukasz Majewski To: Joseph Myers Cc: Zack Weinberg , Wolfgang Denk , GNU C Library , Alistair Francis , Alistair Francis Subject: Re: Accelerating Y2038 glibc fixes Message-ID: <20190730130249.00e1ffaa@jawa> In-Reply-To: References: <20190712072103.D3DBC24003A@gemini.denx.de> <20190726123902.6f8813da@jawa> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/aLJjaEjedMviZpXOladiGPy"; protocol="application/pgp-signature" --Sig_/aLJjaEjedMviZpXOladiGPy Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Joseph, Zack, > On Mon, 29 Jul 2019, Zack Weinberg wrote: >=20 > > I=E2=80=99m prepared to work with you to come up with better wording bu= t I > > need to ask you a bunch of questions. Could you please reply to > > each of the queries marked Qn below? =20 >=20 > 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.) >=20 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 =3D=3D 64, __WORDSIZE =3D=3D 64, __SYSCALL_WORDSIZE =3D=3D 64)= - and ^^^^^^^^^^^^^^^^ - shouldn't be WORDSIZE =3D=3D 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. >=20 > __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). >=20 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 --Sig_/aLJjaEjedMviZpXOladiGPy Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEgAyFJ+N6uu6+XupJAR8vZIA0zr0FAl1AI9kACgkQAR8vZIA0 zr0ZMwgAqLFtF8GmCTQVVOpITsx5XsxoPT89wImKYcINGWvB6sxk532u7s/OC9TC X41/7aQPkE2+FLlmhhOdcsOUU53fQxZAR/nFT8T71nBsX34RMQmWwlJaXjvtMFz2 RNiubjDFA+jf29CjsHe3NrIC1JmRL5x7VdiGh5RFUbBd87IXQUYXt8f5n4Gbmir/ omuSKHtRL2PpcI4xdFXgJkpkNMpGlhDtikm7SgfwfzTobTJUxJEdr8tmPamVfiCi QKooKXxXltSdgKA9Rl6YIuRuyn2uDm3bUdluIOF6A5CqqDRjkXPHLxZaaRklU/HI 209+oQsIBl56mnIHm35dMqiUa9x5sQ== =N1LH -----END PGP SIGNATURE----- --Sig_/aLJjaEjedMviZpXOladiGPy--