git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David A. Wheeler" <dwheeler@dwheeler.com>
To: Rene Rebe <rene@exactcode.de>,
	Matthias-Christian Ott <matthias.christian@tiscali.de>,
	git@vger.kernel.org
Subject: Re: [PATCH GIT 0.6] make use of register variables & size_t
Date: Mon, 25 Apr 2005 14:06:19 -0400	[thread overview]
Message-ID: <426D319B.2040805@dwheeler.com> (raw)
In-Reply-To: <426CD703.5040009@exactcode.de>

Rene Rebe wrote:

> Hi,
>
> Matthias-Christian Ott wrote:
>
>> The "git" didn't try store small variables, which aren't referenced, 
>> in the processor registers. It also didn't use the size_t type. I 
>> corrected a C++ style comment too.
>
>
> Well, modern compilers take register as a non-binding hint. Your 
> register storage specification for those loop counters will not make 
> any change. You have not looked into the resulting binary?

Indeed, register was ALWAYS a non-binding hint. Today,
unless you have specific measurements showing that adding "register"
at some point improves the performance for a (somewhat common) situation,
you're better off NOT including "register" nowadays.  Today's compilers
are generally better at allocating registers than 
people-who-have-little-time.
Premature optimization is the root of all kinds of evil...

> Also // is valid C99 ...

It's not, strictly speaking, okay on old pre-C99 compilers.
But in practice, practically all C compilers from the last 10+ years
have accepted // comments as a very popular extension.
So using "//" is unlikely to be a portability problem, even on semi-old 
compilers.

--- David A. Wheeler


  parent reply	other threads:[~2005-04-25 18:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-25 11:18 [PATCH GIT 0.6] make use of register variables & size_t 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 [this message]
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 19:43           ` the REGISTER thread Brian O'Mahoney
2005-04-25 17:38     ` [PATCH GIT 0.6] make use of register variables & size_t Dmitry Torokhov
2005-04-25 17:51 ` Horst von Brand
     [not found] <3X9X6-5JP-27@gated-at.bofh.it>
2005-04-25 17:36 ` 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>

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=426D319B.2040805@dwheeler.com \
    --to=dwheeler@dwheeler.com \
    --cc=git@vger.kernel.org \
    --cc=matthias.christian@tiscali.de \
    --cc=rene@exactcode.de \
    /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).