[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fe7c52f9-5ff3-95a5-2692-20f81d6decf7@gmail.com>
Date: Fri, 17 Jun 2022 14:13:12 +0200
From: Alejandro Colomar <alx.manpages@...il.com>
To: Cyril Hrubis <chrubis@...e.cz>
Cc: "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>,
Zack Weinberg <zack@...folio.org>,
"ltp@...ts.linux.it" <ltp@...ts.linux.it>,
David Howells <dhowells@...hat.com>
Subject: Ping: [PATCH] uapi: Make __{u,s}64 match {u,}int64_t in userspace
Hi Cyril,
On 12/8/21 16:33, Cyril Hrubis wrote:
> Hi!
>>> 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.
>
> Thinking of this again we can detect C++ as well so it can be safely
> enabled just for C with:
>
> #if !defined(__KERNEL__) && !defined(__cplusplus) && __BITSPERLONG == 64
> # include <asm-generic/int-l64.h>
> #else
> # include <asm-generic/int-ll64.h>
> #endif
>
I'm very interested in seeing this merged, as that would allow
simplifying the man-pages by removing unnecessary kernel details such as
u64[1]. How is the state of this patch?
Cheers,
Alex
[1]:
<https://lore.kernel.org/linux-man/20210423230609.13519-1-alx.manpages@gmail.com/T/#u>
--
Alejandro Colomar
<http://www.alejandro-colomar.es/>
Powered by blists - more mailing lists