linux-kernel - Re: [PATCH 01/24] types: create <asm-generic/int-*.h>

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080425.133030.229754755.davem@davemloft.net>
Date:	Fri, 25 Apr 2008 13:30:30 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jengelh@...putergmbh.de
Cc:	hpa@...or.com, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org
Subject: Re: [PATCH 01/24] types: create <asm-generic/int-*.h>

From: Jan Engelhardt <jengelh@...putergmbh.de>
Date: Fri, 25 Apr 2008 20:27:53 +0200 (CEST)

> On Friday 2008-04-25 01:05, H. Peter Anvin wrote:
> 
> >This creates two generic files with common integer definitions; one
> >where 64 bits is "long" (most 64-bit architectures) and one where 64
> >bits is "long long" (all 32-bit architectures and x86-64.)
> 
> long long is 64 bits on both 32 and 64, is not it?
> If so, the split between 32 and 64 should not be necessary.

Because of the large precendence, if you change this stuff, you're
going to get tons of warnings on the platforms that use "unsigned
long" currently if you change them to use "unsigned long long".

Think about all of the implicit type conversions, argument passing,
et al.

I know because I tried to convert sparc64 over to "unsigned long long"
to make it more like powerpc, and I found quickly that fixing up all
the fallout simply was not worth it.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/