From: Corinna Vinschen <vinschen@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] sh-tdep.c: optimize fv_reg_base_num and dr_reg_base_num
Date: Mon, 16 Feb 2004 16:00:00 -0000 [thread overview]
Message-ID: <20040216160002.GJ18953@cygbert.vinschen.de> (raw)
In-Reply-To: <16432.57749.894105.453337@localhost.redhat.com>
On Feb 16 10:28, Elena Zannoni wrote:
> Corinna Vinschen writes:
> > Hi,
> >
> > another optimization which also will simplify the handling of the
> > upcoming SH variant.
> >
> > The functions fv_reg_base_num and dr_reg_base_num are basically
> > one-liner. The expression they evaluate is fairly simple so
> > I'd suggest the following patch. It converts both functions
> > into macros which will be evaluated inline. This has the additional
> > advantage, that the functions in which they are called have access
> > to gdbarch, which comes in handy for the new SH variant.
> >
> > If the conversion into macros is undesired, I'd like to suggest an
> > alternative implementation. In that case I'd like to add gdbarch as
> > first parameter to both functions.
>
> I prefer to not introduce macros here. Can you explain where you are
> headed? This looks like a micro optimization and I don't see the point
> of it ATM.
Gosh, I'm so sorry. I should have cancled this RFA already days ago.
This is a result of the same thinko I talked about in my previous
mail. The (blockheaded) idea was to use another SH_NUM_REGS for the
new CPU variant than for any other SH type. I already scratched that
but I missed to note that here :-(
Corinna
--
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
next prev parent reply other threads:[~2004-02-16 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 15:15 Corinna Vinschen
2004-02-16 15:32 ` Elena Zannoni
2004-02-16 16:00 ` Corinna Vinschen [this message]
2004-02-16 16:21 ` Elena Zannoni
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=20040216160002.GJ18953@cygbert.vinschen.de \
--to=vinschen@redhat.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