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

Message-ID: <Pine.LNX.4.61.0705222143070.4452@yvahk01.tjqt.qr>
Date:	Tue, 22 May 2007 21:44:32 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Nitin Gupta <nitingupta910@...il.com>
cc:	Andrey Panin <pazke@...pac.ru>, linux-kernel@...r.kernel.org,
	Richard Purdie <richard@...nedhand.com>
Subject: Re: [RFC] LZO1X de/compression support


On May 22 2007 14:38, Nitin Gupta wrote:
> On 5/18/07, Andrey Panin <pazke@...pac.ru> wrote:
>> On 138, 05 18, 2007 at 03:28:31PM +0530, Nitin Gupta wrote:
>> > +     register const unsigned char *ip;
>> 
>> register keyword is meaningless for today's compiler.
>
> But can we assume that gcc is being used? What if we use compiler for
> which it does matter (can't give example for this...)?

How dumb must a compiler be? Although I cannot give an example either,
the register keyword MAY 'clog up' a register, making it harder for
cc to optimally use the whole register set. Imagine we had even less
regs than the x86(_32) already does.


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