linux-kernel - Re: [PATCH 1/4] LOG2: Implement a general integer log2 facility in the kernel [try #4]

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:  <87k639fbtw.fsf@willow.rfc1149.net>
Date:	09 Oct 2006 22:55:55 +0200
From:	Samuel Tardieu <sam@...1149.net>
To:	linux-kernel@...r.kernel.org
Subject:  Re: [PATCH 1/4] LOG2: Implement a general integer log2 facility in the kernel [try #4]

>>>>> "Jan" == Jan Engelhardt <jengelh@...ux01.gwdg.de> writes:

>>  That only offsets the problem a bit.  You still have to derive
>> uint32_t from somewhere.

Jan> The compiler could make it available as a 'fundamental type' -
Jan> i.e.  available without any headers, like 'int' and 'long'.

The compiler isn't allowed to pollute your namespace with symbols like
that. What if someone defines uint32_t as a function for example in
her code? (yes, this would be sick, but is allowed by default)

  Sam
-- 
Samuel Tardieu -- sam@...1149.net -- http://www.rfc1149.net/

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