From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/6995 Path: news.gmane.org!not-for-mail From: Andy Lutomirski Newsgroups: gmane.linux.kernel,gmane.linux.ports.arm.kernel,gmane.linux.lib.musl.general,gmane.comp.lib.glibc.alpha Subject: Re: [PATCHv3 00/24] ILP32 support in ARM64 Date: Wed, 11 Feb 2015 12:15:56 -0800 Message-ID: <54DBB87C.5060901@amacapital.net> References: <20141002155217.GH32147@e104818-lin.cambridge.arm.com> <20150210181302.GA23886@brightrain.aerifal.cx> <20150211190252.GB23507@brightrain.aerifal.cx> <20150211192558.GE23507@brightrain.aerifal.cx> <20150211194741.GI23507@brightrain.aerifal.cx> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1423685775 29515 80.91.229.3 (11 Feb 2015 20:16:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 11 Feb 2015 20:16:15 +0000 (UTC) Cc: Catalin Marinas , Andrew Pinski , "linux-arm-kernel@lists.infradead.org" , LKML , Andrew Pinski , musl@lists.openwall.com, GNU C Library To: "H.J. Lu" , Rich Felker Original-X-From: linux-kernel-owner@vger.kernel.org Wed Feb 11 21:16:08 2015 Return-path: Envelope-to: glk-linux-kernel-3@plane.gmane.org Original-Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YLdhf-00039W-EG for glk-linux-kernel-3@plane.gmane.org; Wed, 11 Feb 2015 21:16:07 +0100 Original-Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753655AbbBKUQB (ORCPT ); Wed, 11 Feb 2015 15:16:01 -0500 Original-Received: from mail-pa0-f50.google.com ([209.85.220.50]:49897 "EHLO mail-pa0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752959AbbBKUQA (ORCPT ); Wed, 11 Feb 2015 15:16:00 -0500 Original-Received: by mail-pa0-f50.google.com with SMTP id hz1so6222560pad.9 for ; Wed, 11 Feb 2015 12:15:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=LwDg/ASfp/B4PM1cWAgrZjGIefmj1dMdyaANX07TlmA=; b=lLhAEcB9VeexCsxRQen//OEMvhxchPYQebZ98rtcMUTEsoGmduTEoTdjZRvEfw4riq f7xAbyLJ6sLensnDA8m/gcFVMcci2JNFNj8PHtkGz0ggQEkIhSpp2BZqLujVz0swPh3d pC0Ytm+i5cc6hYfTtFQKI5yC4VMaZ39HOOCrStT1wW7rClZGjOldSskqcNnkmp/XoYTi K/3VirDzkNKd2oxNfw7FDal9j91r7rS6meGLthGqg4+KuubNqnWntT5JFVzHbusJVJ1g 5kuZIaqIu/j/sUIG+KX9B+aNkPZ6YAJxWG8ReyeiCmfYElhmzQN0wroOLdaRw1wmlDRI JKKQ== X-Gm-Message-State: ALoCoQnPKCAOjbugpAbtwHWBWCJPQXa2jwcvdGSWgmLwrTzGuP17iItwWSbcJXfmCjdrRvtBMXdQ X-Received: by 10.67.21.144 with SMTP id hk16mr515349pad.140.1423685759663; Wed, 11 Feb 2015 12:15:59 -0800 (PST) Original-Received: from amaluto.corp.amacapital.net (50-76-60-73-ip-static.hfc.comcastbusiness.net. [50.76.60.73]) by mx.google.com with ESMTPSA id xx7sm1720574pab.21.2015.02.11.12.15.57 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Feb 2015 12:15:58 -0800 (PST) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 In-Reply-To: Original-Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Xref: news.gmane.org gmane.linux.kernel:1886726 gmane.linux.ports.arm.kernel:392812 gmane.linux.lib.musl.general:6995 gmane.comp.lib.glibc.alpha:49165 Archived-At: On 02/11/2015 11:57 AM, H.J. Lu wrote: >>>> trivially satisfied if you consider x32 and x86_64 separate >>>> compilation environments, but it's not related to the core issue: that >>>> the definition of timespec violates core (not obscure) requirements of >>>> both POSIX and C11. At the time you were probably unaware of the C11 >>>> requirement. Note that it's a LOT harder to effect change in the C >>>> standard, so even if the Austin Group would be amenable to changing >>>> the requirement for timespec to allow something like nseconds_t, >>>> getting WG14 to make this change to work around a Linux/glibc mistake >>>> does not sound practical. >>> >>> That is very unfortunate. I consider it is too late for x32 to change. >> >> Why? It's hardly an incompatible ABI change, as long as the >> kernel/libc fills the upper bits (for old programs that read them >> based on the old headers) when structs are read from the kernel to the >> application, and ignores the upper bits (potentially set or left >> uninitialized by the application) when strings are passed from >> userspace to the kernel. Newly built apps using the struct definition >> with 32-bit tv_nsec would need new libc to ensure that the high bits >> aren't interpreted, but this could be handled by symbol versioning. >> > > We have considered this option. But since kernel wouldn't change > tv_nsec/tv_usec handling just for x32, it wasn't selected. > Did anyone *ask* the kernel people (e.g. hpa)? --Andy