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=-4.0 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 9EC0C1F461 for ; Thu, 18 Jul 2019 19:13:52 +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:from:to:cc:subject:references:date:in-reply-to :message-id:mime-version:content-type; q=dns; s=default; b=AYM17 OUAmKYDhi4MJk+LnjqkNwsX0gjRp+RcYPSm884r/jGSPSkKwK/ExMMHJRaFjXu8E z1/nEclPJjPjjdioaxlujIDVhQ6YOkXGJT45ZqwN6TNMxFCl4K23FUHH0oF5Vb72 A0m3rGR0RKwbJZToyrZn4ZMnRfJ/PHJWjIyw+c= 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:from:to:cc:subject:references:date:in-reply-to :message-id:mime-version:content-type; s=default; bh=rzmNJ7ZPRpg f7NP+PUKP2oi3fok=; b=JwFg7bM9odXHSq+9Rat/yEq1FIYrT1UEKbUDH8GHj6n XDz2UrnvO/OoCnMIjJTRPuqftrcydQaR5SU6Wq/CL85V8Z9U0qqe7+guDKLTn1+o 0s7ql2wWV80RolzQwIDSzJvR5RjmOwgMWNGnICniigbbJ9pbftq1pORefFC3JKnI = Received: (qmail 112523 invoked by alias); 18 Jul 2019 19:13:50 -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 112515 invoked by uid 89); 18 Jul 2019 19:13:50 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: mx1.redhat.com From: Florian Weimer To: Adhemerval Zanella Cc: libc-alpha@sourceware.org Subject: Re: Accelerating Y2038 glibc fixes References: <20190712072103.D3DBC24003A@gemini.denx.de> <874l3mjgi6.fsf@oldenburg2.str.redhat.com> <20190716145216.1C7CE240085@gemini.denx.de> <875zo0911b.fsf@oldenburg2.str.redhat.com> <20190717160021.75EB224003E@gemini.denx.de> <87h87k7ilf.fsf@oldenburg2.str.redhat.com> <20190717181811.5902cd5e@jawa> Date: Thu, 18 Jul 2019 21:13:45 +0200 In-Reply-To: (Adhemerval Zanella's message of "Thu, 18 Jul 2019 15:53:28 -0300") Message-ID: <87ftn3xija.fsf@oldenburg2.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain * Adhemerval Zanella: > So what about to not add a user-selected way to set the time_t size > (as off_t) and just enable time64_t support and sets is as default for > build with a minimum kernel of v5.1 (if I recall correctly as being the > one that added time64 support)? Does this mean that some developers see a glibc 2.31 with a 32-bit time_t on i386, and others see a 64-bit time_t? > It will move all time32 support as compat symbols for the required ABI, > without an option to select it through a build flag. Newer ports will > just have the expected symbol names, no tinkering needed. But if we build glibc with pre-5.1 kernel headers, you will get the legacy interface? Thanks, Florian