From: Andrew Cagney <ac131313@redhat.com>
To: Paul Hilfinger <hilfingr@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: Changes to allow extensions to operator set
Date: Thu, 04 Sep 2003 02:18:00 -0000 [thread overview]
Message-ID: <3F56A03E.5020106@redhat.com> (raw)
In-Reply-To: <20030901093941.0D2E9F2A64@nile.gnat.com>
> 4. I removed register declarations in routines I touched, just on
> general principles. [I believe that all register declarations in
> GDB and much other GNU software are anachronistic holdovers from
> some bygone era. GCC ignores them, or so I'm told, except to
> insure that & is not applied to register variables. Furthermore,
> my impression is that many of these declarations would be
> inappropriate even in non-optimizing compilers, since they often
> seem to be used rather indiscriminantly in ways that are likely to
> favor putting the wrong things into registers.]
BTW,
This is a separate but obvious (and tedious) change (you'll notice I
occasionally expunge "register" from random files). Can you first up
just expunge the "register" on the files you're interested in? Doing
this keeps the cosmetic and functional changes separate.
Oh, gdb.base/store.exp abuses "register" to create a few test senarios.
enjoy,
Andrew
next prev parent reply other threads:[~2003-09-04 2:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 9:39 Paul Hilfinger
2003-09-04 2:18 ` Andrew Cagney [this message]
2003-09-05 8:32 ` Paul Hilfinger
2003-09-05 15:57 ` Andrew Cagney
2003-09-05 16:23 ` Andrew Cagney
2003-09-06 11:13 ` Paul Hilfinger
2003-09-11 18:55 ` Andrew Cagney
2003-09-13 8:58 ` Paul Hilfinger
2003-09-18 9:20 ` Paul Hilfinger
2003-09-22 17:04 ` Andrew Cagney
2003-09-05 16:29 ` Andrew Cagney
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=3F56A03E.5020106@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=hilfingr@gnat.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