From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@gnu.org>
Cc: eggert@cs.ucla.edu, 11617@debbugs.gnu.org
Subject: bug#11617: Don't use 'register'; these days it's not needed.
Date: Sun, 03 Jun 2012 18:09:07 +0300 [thread overview]
Message-ID: <83r4twbffw.fsf@gnu.org> (raw)
In-Reply-To: <87ipf8tpph.fsf@gnu.org>
> From: Chong Yidong <cyd@gnu.org>
> Cc: Paul Eggert <eggert@cs.ucla.edu>, 11617@debbugs.gnu.org
> Date: Sun, 03 Jun 2012 22:50:02 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Attached is a patch to remove 'register' from the mainline
> >> Emacs source code.
> >
> > FWIW, I see no compelling reason for this change, even after I've read
> > the explanations. This keyword is a cue to the compiler, so it in
> > general conveys non-trivial information. If today's compilers mostly
> > ignore that, it doesn't mean this will always be the state of affairs.
> > However, by removing this, we lose those cues forever.
>
> I wonder how many of those register variables were actually added after
> profiling to see if they make any difference. My guess is none,
> i.e. those keywords are bogus.
??? I don't necessarily see the connection between profiling and the
keyword uses. The way I see it, these are cues to the compiler, they
tell which of the variables are accessed in the inner loops and more
intensively, under the expected data flow.
next prev parent reply other threads:[~2012-06-03 15:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 6:06 bug#11617: Don't use 'register'; these days it's not needed Paul Eggert
2012-06-03 14:24 ` Eli Zaretskii
2012-06-03 14:50 ` Chong Yidong
2012-06-03 15:09 ` Eli Zaretskii [this message]
2012-06-03 15:22 ` Stefan Monnier
2012-06-03 16:33 ` Paul Eggert
2012-06-04 13:06 ` Stefan Monnier
2012-06-04 14:40 ` Paul Eggert
2012-06-04 19:30 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r4twbffw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11617@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=eggert@cs.ucla.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).