From: Mark Kettenis <kettenis@chello.nl>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [wip/rfc] Merge REGISTER_TO_VALUE and REGISTER_TO_TYPE
Date: Wed, 04 Jun 2003 21:45:00 -0000 [thread overview]
Message-ID: <8665nl34ao.fsf@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: Andrew Cagney's message of "Wed, 04 Jun 2003 15:38:06 -0400"
Andrew Cagney <ac131313@redhat.com> writes:
[snip]
> With this in mind, I'm thinking that REGISTER_TO_TYPE and
> REGISTER_TO_VALUE should be merged. To that end, I can see several ways
> of doing it:
>
> - Don't merge - add REGISTER_TO_TYPE to the architecture vector
>
> - Retain the current logic - just apply REGISTER_TO_VALUE to values
> stored across multiple registers
>
> - Add a frame parameter to REGISTER_TO_VALUE and make it responsible for
> both extracting the bytes from the register[s] and then storing them in
> the ``struct value''.
>
> The last option is interesting, it would let the target draw the value
> from any register based on REGNUM. The i386 with its long-long problem
> might be interested in this (you'll notice in the patch I made an
> attempt at doing this only I didn't see it affect the test results).
>
> Thoughts?
The last option is certainly attractive. The fact that this doesn't
show any improvements in the testsuite, is because there is no test
for `long long' in store.exp. There are tests for small structs there
that will still fail since your implementation of
i386_register_to_value isn't complete; it should also handle 8-byte
strcutures stored in registers. Not just integers.
Anyway, you can leave the i386-specific details to me if you prefer.
Mark
next prev parent reply other threads:[~2003-06-04 21:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 19:38 Andrew Cagney
2003-06-04 21:45 ` Mark Kettenis [this message]
2003-06-04 23:05 ` Andrew Cagney
2003-06-06 18:12 ` [cagney_convert-20030606-branch] Add value to REGISTER_TO_VALUE et.al Andrew Cagney
2003-06-08 16:43 ` Mark Kettenis
2003-06-08 17:15 ` Andrew Cagney
2003-06-08 22:11 ` Andrew Cagney
2003-06-08 22:51 ` Mark Kettenis
2003-06-09 0:22 ` Andrew Cagney
2003-06-09 9:35 ` Mark Kettenis
2003-06-09 14:38 ` Andrew Cagney
2003-06-09 9:38 ` Mark Kettenis
2003-06-09 14:20 ` Andrew Cagney
2003-06-09 17:43 ` Mark Kettenis
2003-06-09 10:26 ` Mark Kettenis
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=8665nl34ao.fsf@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=ac131313@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