linux-kernel - Re: [RFC] LZO1X de/compression support

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]

Message-ID: <46546D37.5030106@goop.org>
Date:	Wed, 23 May 2007 17:35:03 +0100
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Bernd Petrovitsch <bernd@...mix.at>
CC:	Nitin Gupta <nitingupta910@...il.com>,
	Andrey Panin <pazke@...pac.ru>, linux-kernel@...r.kernel.org,
	Richard Purdie <richard@...nedhand.com>
Subject: Re: [RFC] LZO1X de/compression support

Bernd Petrovitsch wrote:
> The "register" keyword is and was always from start *at most* a hint to
> the C compiler to use a register for that variable (similar to "inline"
> BTW).
> So every C compiler is allowed to simply ignore the "register" for any
> reason - be it "not implemented" or "the compiler knows better".
> Trivial reason: Think of a function with 100 register variables.
>   

The only useful semantic for "register" these days is that its illegal
to take the address of one.  So it might be useful if you want to make
sure you have no aliases of a particular variable.

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