From: Jim Blandy <jimb@redhat.com>
To: "Theodore A. Roth" <troth@openavr.org>
Cc: gdb@sources.redhat.com
Subject: Re: Function addresses on the AVR
Date: Fri, 13 Jun 2003 20:32:00 -0000 [thread overview]
Message-ID: <vt265n9sops.fsf@zenia.home> (raw)
In-Reply-To: <Pine.LNX.4.53.0306111047490.20510@knuth.amplepower.com>
"Theodore A. Roth" <troth@openavr.org> writes:
> I've changed the ADDRESS_TO_POINTER and POINTER_TO_ADDRESS methods to
> do the bit shift for code addrs and removed the
> CONVERT_FROM_FUNC_PTR_ADDR method. I can't see that it negatively
> affects either what is in cvs or the new code I'm working on
> (frame-ifying the avr), so it looks like your analysis is correct.
>
> I'll commit the changes after I've done a bit more testing (I still
> don't have the testsuite running for avr yet :-\ ). That will remove
> one more instance of CONVERT_FROM_FUNC_PTR_ADDR for you.
Great --- thanks!
> Thanks for digging through the avr stuff.
No problem!
prev parent reply other threads:[~2003-06-13 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 7:45 Jim Blandy
2003-06-11 18:07 ` Theodore A. Roth
2003-06-13 20:32 ` Jim Blandy [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=vt265n9sops.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=troth@openavr.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