From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [rfc] Make register_type calls more consistent
Date: Sun, 21 Jan 2007 17:37:00 -0000 [thread overview]
Message-ID: <20070121173751.GH12463@nevyn.them.org> (raw)
In-Reply-To: <20070110213809.GA16137@nevyn.them.org>
On Wed, Jan 10, 2007 at 04:38:09PM -0500, Daniel Jacobowitz wrote:
> I just changed all places calling their own foo_register_type method or
> gdbarch_register_type to call register_type, and added a comment;
> hopefully between the two changes, it won't recur. Calling
> register_type is marginally more efficient since it caches the types
> without having lots of branches.
>
> OK?
I've checked this in; it was tested earlier on x86_64-pc-linux-gnu.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-01-21 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-10 21:38 Daniel Jacobowitz
2007-01-21 17:37 ` Daniel Jacobowitz [this message]
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=20070121173751.GH12463@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.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