From: Daniel Berlin <dberlin@dberlin.org>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: i Andrew Cagney <ac131313@cygnus.com>, <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] Type cleanups
Date: Mon, 13 May 2002 12:54:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0205131544530.21539-100000@dberlin.org> (raw)
In-Reply-To: <20020513184651.GA16618@nevyn.them.org>
> > cache, and no one has noticed me adding another assertion to every
> > gdbarch accessor function, I don't expect changing the above to opaque
> > to be a significant problem :-)
>
> I think you may be underestimating the frequency of some of the TYPE
> accessors... but if I get a chance, I'll benchmark it.
If worst comes to worst, you can always make them static inlines in the
header.
That way, you can still debug them easily, but if optimization is on, ....
--Dan
next prev parent reply other threads:[~2002-05-13 19:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-12 17:34 Daniel Jacobowitz
2002-05-12 20:18 ` Andrew Cagney
2002-05-12 20:40 ` Daniel Jacobowitz
2002-05-12 21:31 ` Andrew Cagney
2002-05-13 11:46 ` Daniel Jacobowitz
2002-05-13 12:54 ` Daniel Berlin [this message]
2002-05-13 12:57 ` Daniel Jacobowitz
2002-05-13 6:59 ` Daniel Jacobowitz
2002-05-13 8:37 ` Andrew Cagney
2002-05-13 8:51 ` Elena Zannoni
2002-05-13 9:11 ` Andrew Cagney
2002-05-13 9:19 ` Elena Zannoni
2002-05-13 11:50 ` Daniel Jacobowitz
2002-05-13 11:59 ` Daniel Jacobowitz
2002-05-13 15:14 ` Andrew Cagney
2002-05-13 16:09 ` Daniel Jacobowitz
2002-05-13 18:37 ` Elena Zannoni
2002-05-14 17:09 ` Andrew Cagney
2002-05-17 1:11 ` Eli Zaretskii
2002-05-17 8:02 ` Daniel Jacobowitz
2002-05-17 9:14 ` Eli Zaretskii
2002-05-17 10:21 ` Daniel Jacobowitz
2002-05-17 10:34 ` Andrew Cagney
2002-05-18 0:15 ` Eli Zaretskii
2002-05-18 0:13 ` Eli Zaretskii
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=Pine.LNX.4.44.0205131544530.21539-100000@dberlin.org \
--to=dberlin@dberlin.org \
--cc=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.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