Re: [PATCH v6 05/19] arm64:uapi: set __BITS_PER_LONG correctly for ILP32 and LP64

2015-12-03 Thread Dr. Philipp Tomsich
Catalin, > Quick question: IIRC, earlier aarch64 gcc versions did not generate > __ILP32__ when -mabi=ilp32, they only removed __LP64__. When did the > change happen? Could we assume that all compiler versions used to > generate ILP32 would define this? The __ILP32__ define has been supported sin

Re: [PATCH v6 05/19] arm64:uapi: set __BITS_PER_LONG correctly for ILP32 and LP64

2015-12-03 Thread Catalin Marinas
On Wed, Nov 18, 2015 at 12:16:45AM +0300, Yury Norov wrote: > diff --git a/arch/arm64/include/uapi/asm/bitsperlong.h > b/arch/arm64/include/uapi/asm/bitsperlong.h > index fce9c29..4265243 100644 > --- a/arch/arm64/include/uapi/asm/bitsperlong.h > +++ b/arch/arm64/include/uapi/asm/bitsperlong.h > @

[PATCH v6 05/19] arm64:uapi: set __BITS_PER_LONG correctly for ILP32 and LP64

2015-11-17 Thread Yury Norov
From: Andrew Pinski Define __BITS_PER_LONG depending on the ABI used (i.e. check whether __ILP32__ or __LP64__ is defined). This is necessary for glibc to determine the appropriate type definitions for the system call interface. Reviewed-by: David Daney Signed-off-by: Philipp Tomsich Signed-