From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Bernd Petrovitsch <bernd@firmix.at>
Cc: Nitin Gupta <nitingupta910@gmail.com>,
Andrey Panin <pazke@donpac.ru>,
linux-kernel@vger.kernel.org,
Richard Purdie <richard@openedhand.com>
Subject: Re: [RFC] LZO1X de/compression support
Date: Wed, 23 May 2007 17:35:03 +0100 [thread overview]
Message-ID: <46546D37.5030106@goop.org> (raw)
In-Reply-To: <1179869082.3649.6.camel@gimli.at.home>
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
next prev parent reply other threads:[~2007-05-23 16:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 9:58 [RFC] LZO1X de/compression support Nitin Gupta
2007-05-18 10:14 ` Heikki Orsila
2007-05-18 11:27 ` Nitin Gupta
2007-05-18 11:53 ` Richard Purdie
2007-05-18 10:42 ` Pekka Enberg
2007-05-18 10:53 ` Pekka Enberg
2007-05-22 8:54 ` Nitin Gupta
2007-05-22 8:59 ` Pekka Enberg
2007-05-22 9:10 ` Nitin Gupta
2007-05-22 9:34 ` Pekka Enberg
2007-05-18 11:11 ` Andrey Panin
2007-05-22 9:08 ` Nitin Gupta
2007-05-22 19:44 ` Jan Engelhardt
2007-05-22 21:24 ` Bernd Petrovitsch
2007-05-23 16:35 ` Jeremy Fitzhardinge [this message]
2007-05-18 11:46 ` Richard Purdie
2007-05-22 9:19 ` Nitin Gupta
2007-05-18 20:04 ` Matt Mackall
2007-05-18 21:14 ` Krzysztof Halasa
2007-05-19 18:55 ` Bill Rugolsky Jr.
2007-05-19 21:52 ` Richard Purdie
2007-05-22 19:40 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2007-05-19 18:12 devzero
2007-05-20 11:42 Tomasz Chmielewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46546D37.5030106@goop.org \
--to=jeremy@goop.org \
--cc=bernd@firmix.at \
--cc=linux-kernel@vger.kernel.org \
--cc=nitingupta910@gmail.com \
--cc=pazke@donpac.ru \
--cc=richard@openedhand.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).