[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a26ab9bfc27a430bb8a7b6aa2f39d724@AcuMS.aculab.com>
Date: Tue, 21 Jun 2022 13:04:04 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Cyril Hrubis' <chrubis@...e.cz>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: "linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
"linux-api@...r.kernel.org" <linux-api@...r.kernel.org>,
"libc-alpha@...rceware.org" <libc-alpha@...rceware.org>,
"arnd@...db.de" <arnd@...db.de>,
"ltp@...ts.linux.it" <ltp@...ts.linux.it>,
"zack@...folio.org" <zack@...folio.org>,
"dhowells@...hat.com" <dhowells@...hat.com>
Subject: RE: [PATCH v3] uapi: Make __{u,s}64 match {u,}int64_t in userspace
From: Cyril Hrubis
> Sent: 21 June 2022 13:04
>
> This changes the __u64 and __s64 in userspace on 64bit platforms from
> long long (unsigned) int to just long (unsigned) int in order to match
> the uint64_t and int64_t size in userspace for C code.
>
> We cannot make the change for C++ since that would be non-backwards
> compatible change and may cause possible regressions and even
> compilation failures, e.g. overloaded function may no longer find a
> correct match.
Isn't is enough just to mention C++ name mangling?
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists