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 654E31F463 for ; Wed, 25 Sep 2019 16:29:09 +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:in-reply-to:message-id :references:mime-version:content-type; q=dns; s=default; b=mFIa3 nIBXhGuHYirV4c1nm3VGSj1DQPGEwqEKavxnsS2Gq2d7iB3uaADYPE+uN6JODtdx TCrdtfePl8FWOvo4C8oOp3kA8AXaWdKcPOaEaBZrumjghqTUkNaZY+7cqGZg6qEC bWPdNFXQP0ZvjPuvSKdBTDsVbG5dHfiZ4N2xFg= 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:in-reply-to:message-id :references:mime-version:content-type; s=default; bh=ehj0HMByrSf LL6+LugGsK91O6kY=; b=b7siJQfH96H24oXteS0p4n08EWxIbPApo7M/Z7/Jhl5 yElUZ0Dpqy/Q8e6Q0IaX6JnqzEmzHcdAwPv9b8gRePFCW7ELcuMQyHMaUyazhtuO rUeYux9+zWaArxnD8Q+cGqLRcEiH9n4qPMEdWDz8QoyxyEqcL3dc4/uLPDXX1q+Y = Received: (qmail 31665 invoked by alias); 25 Sep 2019 16:29:07 -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 31657 invoked by uid 89); 25 Sep 2019 16:29:06 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: esa1.mentor.iphmx.com IronPort-SDR: fA1Sl6uk94vpUcqajrexEEaoqcEuJ7Y9Pl2NI0lHT3ARmlVcyeUyPODiIiC3zLGaNuZJ5zu/qn rAzc7B4+wuCVmirYsYABVouErPI8Ef2x0KiVtiVY9rSIgbC5FgrQIZ8ckhTLUSrZvhcsc6vnmR RV8TLm5keCWizz7Gsgmm5HgVzvImj/Hhu/BwqQZbag9LCw7TH/lXLjGmhwSexBI6NbuTL9VgDY r4VqTshws+55/pslTNj5wuE0P5t5cEDKXr8X6ObrSbGwBim2MHvtXJBLkwwvs1lRHsx1FTgwTE DhQ= IronPort-SDR: yTFJZpfjlr08O88QU+9Fsg129ZWo9OWQetdb7+RdJFj3EI2dJ5DkIHL96VDwtov46DPPF2VsVm Moz7oZfd5681eqzwbbbbIlUetoUWSZSmBbqhwMpMT9Wz9crF5W0EZR0Uzz5qnCnzpe3TrihUNQ JaHV2CaQdz1b6rEmR/1xca4hTZzmZ9PbVky399kNUgxLU/zO+BR+opw48KZowMJ3bHENNE50On v/wrhwh/we9/bK8tfd4TwY024xjH4vjfiraowOJ0XUEEZslrvWpE2/8i7B/DNXlivgicdv9zb0 WZQ= Date: Wed, 25 Sep 2019 16:28:58 +0000 From: Joseph Myers To: Lukasz Majewski CC: Florian Weimer , Alistair Francis , Alistair Francis , Zack Weinberg , Arnd Bergmann , GNU C Library , Adhemerval Zanella , Florian Weimer , Carlos O'Donell , Stepan Golosunov Subject: Re: [PATCH v8 1/3] y2038: Introduce internal for glibc struct __timespec64 In-Reply-To: <20190925163818.5e8a3a03@jawa> Message-ID: References: <20190918211603.8444-1-lukma@denx.de> <20190918211603.8444-2-lukma@denx.de> <20190923232109.735f898b@jawa> <20190925094540.14be491d@jawa> <877e5wtu7y.fsf@mid.deneb.enyo.de> <20190925153402.060a686c@jawa> <87lfucsddd.fsf@mid.deneb.enyo.de> <20190925163818.5e8a3a03@jawa> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" On Wed, 25 Sep 2019, Lukasz Majewski wrote: > Let's wait for Joseph's opinion if we shall replace named padding struct > members with unnamed bitfields (and drop potential support for fixing > issues, which would require explicit clearing of padding before passing > data to the kernel). I'm not particularly concerned with whether this patch uses named padding, unnamed bit-field or 64-bit tv_nsec in the internal struct __timespec64. (I don't think a named bit-field would make sense there, however.) If we use an unnamed bit-field now we can readily change it later to have a name if we decide to support clearing padding for compat syscalls for kernels 5.1.0 to 5.1.4. -- Joseph S. Myers joseph@codesourcery.com