From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18013 invoked by alias); 26 Feb 2013 23:58:23 -0000 Received: (qmail 17994 invoked by uid 22791); 26 Feb 2013 23:58:22 -0000 X-SWARE-Spam-Status: No, hits=-3.0 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from toast.topped-with-meat.com (HELO topped-with-meat.com) (204.197.218.159) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 26 Feb 2013 23:58:16 +0000 Received: by topped-with-meat.com (Postfix, from userid 5281) id 8B2A02C088; Tue, 26 Feb 2013 15:58:14 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Roland McGrath To: Rich Felker Cc: Carlos O'Donell , GNU C Library , libc-ports@sourceware.org Subject: Re: [RFC] Copy as much as you can during a 32-bit stat before returning EOVERFLOW? In-Reply-To: Rich Felker's message of Tuesday, 26 February 2013 18:48:49 -0500 <20130226234849.GH20323@brightrain.aerifal.cx> References: <512D1335.1020704@redhat.com> <20130226234849.GH20323@brightrain.aerifal.cx> Message-Id: <20130226235814.8B2A02C088@topped-with-meat.com> Date: Tue, 26 Feb 2013 23:58:00 -0000 X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=LYSvtFvi c=1 sm=1 tr=0 a=WkljmVdYkabdwxfqvArNOQ==:117 a=14OXPxybAAAA:8 a=DQCEwa3zsEMA:10 a=Z6MIti7PxpgA:10 a=kj9zAlcOel0A:10 a=hOe2yjtxAAAA:8 a=R0K8r3JO6igA:10 a=fQggqZfGdBMJZJVt7w0A:9 a=CjuIK1q_8ugA:10 X-IsSubscribed: yes Mailing-List: contact libc-ports-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: libc-ports-owner@sourceware.org X-SW-Source: 2013-02/txt/msg00069.txt.bz2 > Stage 1: Change the default for _FILE_OFFSET_BITS to 64 on all > targets, and make 32-bit off_t accessible only by explicitly > requesting -D_FILE_OFFSET_BITS=32. This should help transition all the > stragglers who are just straggling because they don't know better; the > few who have fundamentally buggy code that's incompatible with 64-bit > off_t can use the workaround (-D_FILE_OFFSET_BITS=32) until they get > their acts together. This makes library ABIs silently become incompatible with past builds. That's a non-starter. I'm somewhat sympathetic to the overall goal, but I'm not at all sure what a viable migration path might be. Regardless, don't hijack this thread for that subject. Start your own thread. Thanks, Roland