[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YbDQW6uakG3XD8jV@yuki>
Date: Wed, 8 Dec 2021 16:33:47 +0100
From: Cyril Hrubis <chrubis@...e.cz>
To: David Howells <dhowells@...hat.com>
Cc: Zack Weinberg <zack@...folio.org>, Arnd Bergmann <arnd@...db.de>,
"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
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
--
Cyril Hrubis
chrubis@...e.cz
Powered by blists - more mailing lists