[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <913509.1638457313@warthog.procyon.org.uk>
Date: Thu, 02 Dec 2021 15:01:53 +0000
From: David Howells <dhowells@...hat.com>
To: "Zack Weinberg" <zack@...folio.org>
Cc: dhowells@...hat.com, "Arnd Bergmann" <arnd@...db.de>,
"Cyril Hrubis" <chrubis@...e.cz>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
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
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.
David
Powered by blists - more mailing lists