From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/14554 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.comp.lib.glibc.alpha,gmane.linux.lib.musl.general Subject: Re: [musl] time64 abi choices for glibc and musl Date: Mon, 12 Aug 2019 13:55:56 -0400 Message-ID: <20190812175556.GT9017@brightrain.aerifal.cx> References: <20190810175808.GA13205@brightrain.aerifal.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="135771"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mutt/1.5.21 (2010-09-15) Cc: musl@lists.openwall.com To: libc-alpha@sourceware.org Original-X-From: libc-alpha-return-104324-glibc-alpha=m.gmane.org@sourceware.org Mon Aug 12 19:56:05 2019 Return-path: Envelope-to: glibc-alpha@blaine.gmane.org Original-Received: from server1.sourceware.org ([209.132.180.131] helo=sourceware.org) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hxEY8-000ZCR-9p for glibc-alpha@blaine.gmane.org; Mon, 12 Aug 2019 19:56:04 +0200 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:references :mime-version:content-type:in-reply-to; q=dns; s=default; b=gY8E lLKWNkNphCx42ZiYo10efZSNSwfG6fb6k2dQ2zCFbnXaabqhyviTN8phBKC9iAf3 733McKdf3oFy96d22uCTvgNFuAd42uwpGTXYVk/R4oy9hBbzOGwniuFGcC0a0o1f d6bz32+1LRWfjxxWJAISaF0CwpfoUFzuNOmX6So= 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:references :mime-version:content-type:in-reply-to; s=default; bh=HKDptup00r 0Hd1KgSwEi8y2/nsI=; b=dwPjVN+yb15dDOoUedFaGnCy8jtnNn2Od0ghxQUY9t 1GqJFl0BpexYt57aH4LUgf34ByUE39bDAU6sfyvmiFH53VnV9kpRATlHvjz6BC0R OT+aEkR8ZSHG13IuJ0hSEOe4AiPeLiFBPSdcapR5mYKAl7s9KcaDC9ir5FPBQNMy I= Original-Received: (qmail 83711 invoked by alias); 12 Aug 2019 17:55:59 -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: , Original-Sender: libc-alpha-owner@sourceware.org Original-Received: (qmail 83703 invoked by uid 89); 12 Aug 2019 17:55:59 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: brightrain.aerifal.cx Content-Disposition: inline In-Reply-To: <20190810175808.GA13205@brightrain.aerifal.cx> Xref: news.gmane.org gmane.comp.lib.glibc.alpha:96679 gmane.linux.lib.musl.general:14554 Archived-At: On Sat, Aug 10, 2019 at 01:58:08PM -0400, Rich Felker wrote: > Note: this email is to glibc list and particularly seeking feedback > from glibc folks, but CC'd to musl list as well. > > As far as I can tell, most time64 work/discussion on the glibc side so > far has been about implementation mechanisms and symbol-binding ABI > aspects, and one aspect that doesn't seem to have been addressed is > making good choices about the actual types involved. Some of them have > been done: > > struct timespec (endian-matching padding) > struct timeval (64-bit suseconds_t) > struct itimerspec, itimerval, utimbuf, timeb (obvious definitions) > > but I haven't seen a clear proposal with rationale for the choices in > defining: > > struct stat > struct msqid_ds, semid_ds, shmid_ds (sysvipc) > struct rusage > struct timex > struct utmp[x] > > [...] The wiki at https://sourceware.org/glibc/wiki/Y2038ProofnessDesign does not seem to cover any of this issue, and the two branch links that should shed light on the types seem to be down/deleted: https://sourceware.org/git/?p=glibc.git;a=log;h=refs/heads/aaribaud/y2038-2.26 https://sourceware.org/git/?p=glibc.git;a=log;h=refs/heads/aaribaud/y2038-2.26-rfc-2 I'm guessing the following is the current one that should be linked instead, no? https://sourceware.org/git/?p=glibc.git;a=log;h=refs/heads/aaribaud/y2038 Rich