[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1e3867cd-2c8b-4fe1-93a6-c6ae34120f6b@www.fastmail.com>
Date: Thu, 02 Dec 2021 15:48:21 -0500
From: "Zack Weinberg" <zack@...folio.org>
To: "David Howells" <dhowells@...hat.com>
Cc: "linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
"Florian Weimer" <libc-alpha@...rceware.org>,
"linux-api@...r.kernel.org" <linux-api@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"David Laight" <David.Laight@...lab.com>,
"ltp@...ts.linux.it" <ltp@...ts.linux.it>
Subject: Re: [PATCH] uapi: Make __{u,s}64 match {u,}int64_t in userspace
On Thu, Dec 2, 2021, at 10:01 AM, David Howells via Libc-alpha wrote:
> Zack Weinberg <zack@...folio.org> wrote:
>> I could be persuaded otherwise with an example of a program for which
>> changing __s64 from 'long long' to 'long' would break *binary* backward
>> compatibility, or similarly for __u64.
>
> C++ could break.
That's too hypothetical to be actionable. I would like to see a _specific program_, and I would like it to be one that already exists in the world and was not written as a test case for this hypothetical ABI break.
zw
Powered by blists - more mailing lists