From: Kevin Buettner <kevinb@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>, Michael Snyder <msnyder@redhat.com>
Cc: Elena Zannoni <ezannoni@redhat.com>,
Michael Snyder <msnyder@cygnus.com>,
gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Export fill_fpxregset
Date: Thu, 10 Jan 2002 12:14:00 -0000 [thread overview]
Message-ID: <1020110201246.ZM5464@localhost.localdomain> (raw)
In-Reply-To: Daniel Jacobowitz <drow@mvista.com> "Re: [PATCH] Export fill_fpxregset" (Jan 10, 2:56pm)
On Jan 10, 2:56pm, Daniel Jacobowitz wrote:
> > In this case, i386-linux-nat.c uses the native type elf_fpxregset_t,
> > while the rest of gdb will use the portable type gdb_fpxregset_t.
> > Since they are identical, there shouldn't be a problem.
>
> I don't think there should be a gdb_fpxregset_t. There's no such thing
> as a portable fpxregset; PowerPC is going to have a vrregset instead,
> in fact. How this should be handled in generic code that wants to
> manipulate regsets remains to be seen. Ideal might be a list of
> available regset types in a struct somewhere.
In my opinion an xregset ought to just be passed as a void *. The
underlying target code will need a method which may be called to tell
the generic code the size (for allocation and copying purposes).
If you want type safety, you can wrap the the pointer in a struct
and pass the struct.
Kevin
prev parent reply other threads:[~2002-01-10 20:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 14:33 Michael Snyder
2002-01-09 15:02 ` Daniel Jacobowitz
2002-01-09 16:04 ` Elena Zannoni
2002-01-10 11:52 ` Michael Snyder
2002-01-10 11:56 ` Daniel Jacobowitz
2002-01-10 12:14 ` Kevin Buettner [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=1020110201246.ZM5464@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=drow@mvista.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@cygnus.com \
--cc=msnyder@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