linux-kernel - Re: [2.6 patch] asm-generic/int-ll64.h: always provide _

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] [day] [month] [year] [list]

Date:	Tue, 20 May 2008 07:54:18 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Adrian Bunk <bunk@...sta.de>
CC:	Harvey Harrison <harvey.harrison@...il.com>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [2.6 patch] asm-generic/int-ll64.h: always provide __{s,u}64

Adrian Bunk wrote:
> 
> $ cat test.c
> #include <stdio.h>
> 
> int main()
> {
> #ifdef __i486__
>   printf("foobarbaz\n");
> #endif
> 
>   return 0;
> }

*Groan* you're right.  Blitering idiots... they only present __i386__ 
and whatever *exact* CPU you have -march= for, which of course is a 
*CHANGING SET* (just __i486__, __i586__ and __i686__ isn't enough... 
they seem to also have __core2__, __k8__ and $DEITY knows what else.)

The only sensible way to handle that would be to centralize that 
knowledge in a header file.

	-hpa
--
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/