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: <1179869082.3649.6.camel@gimli.at.home>
Date:	Tue, 22 May 2007 23:24:42 +0200
From:	Bernd Petrovitsch <bernd@...mix.at>
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 Tue, 2007-05-22 at 14:38 +0530, 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

Yes.
If another compiler wants to compile the kernel, it must have
implemented various widely used gcc extensions.

> which it does matter (can't give example for this...)?

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.

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services

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