git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>"  <7eggert@gmx.de>
To: Matthias-Christian Ott <matthias.christian@tiscali.de>,
	Linus Torvalds <torvalds@osdl.org>,
	git@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH GIT 0.6] make use of register variables & size_t
Date: Tue, 26 Apr 2005 20:18:02 +0200	[thread overview]
Message-ID: <E1DQUdL-0000rx-P3@be1.7eggert.dyndns.org> (raw)
In-Reply-To: 3XfpD-21C-11@gated-at.bofh.it

Matthias-Christian Ott <matthias.christian@tiscali.de> wrote:

> And if you think "register" variables are outdated, please remove the
> CONFIG_REGPARM option from the Kernel source.

Register variables are outdated because they hinder the compiler from
optimizing by taking away 1/7 of the usable registers on x86. Use six
register variables and you're back to a accumulator-machine.
Use -O2 or -Os instead, the compiler is smarter than you.

The regparm calling convention will change the
load value -> store value on stack -> call sequence into
load value -> call -> store if needed
Obviously the second form can be better optimized than the first one.
Therefore it's a gain instead of a loss.

If you really want to help the compiler, look for something like repeated
pointer dereference or access to global variables and cache them in block-
local variables (pointers, int and uint only, even for caching chars).
Beware of volatile variables, and don't forget to look at the assembler code.
-- 
The generation of random numbers is too important to be left to chance. 


  parent reply	other threads:[~2005-04-26 18:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3X9X6-5JP-27@gated-at.bofh.it>
2005-04-25 17:36 ` [PATCH GIT 0.6] make use of register variables & size_t Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
     [not found] ` <3Xdel-8u2-43@gated-at.bofh.it>
     [not found]   ` <3XfpD-21C-11@gated-at.bofh.it>
2005-04-26 18:18     ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org> [this message]
2005-04-25 11:18 Matthias-Christian Ott
2005-04-25 11:39 ` Rene Rebe
2005-04-25 12:56   ` Matthias-Christian Ott
2005-04-25 13:01     ` Matthias-Christian Ott
2005-04-25 18:06   ` David A. Wheeler
2005-04-25 12:32 ` Petr Baudis
2005-04-25 13:07   ` Pekka Enberg
2005-04-25 14:52 ` Linus Torvalds
2005-04-25 16:59   ` Matthias-Christian Ott
2005-04-25 17:12     ` Jan-Benedict Glaw
2005-04-25 17:13       ` Thomas Glanzmann
2005-04-25 17:18         ` Jan-Benedict Glaw
2005-04-25 18:23           ` Matthias-Christian Ott
2005-04-25 17:22     ` Valdis.Kletnieks
2005-04-25 17:23     ` Linus Torvalds
2005-04-25 18:15       ` Matthias-Christian Ott
2005-04-25 18:50         ` Linus Torvalds
2005-04-25 20:50           ` Arjan van de Ven
2005-04-25 18:55         ` Valdis.Kletnieks
2005-04-25 17:38     ` Dmitry Torokhov
2005-04-25 17:51 ` Horst von Brand

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=E1DQUdL-0000rx-P3@be1.7eggert.dyndns.org \
    --to=7eggert@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.christian@tiscali.de \
    --cc=torvalds@osdl.org \
    /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).