From: Daniel Jacobowitz <drow@mvista.com>
To: 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 11:56:00 -0000 [thread overview]
Message-ID: <20020110145653.B10383@nevyn.them.org> (raw)
In-Reply-To: <3C3DEFCE.B5A19EFC@redhat.com>
On Thu, Jan 10, 2002 at 11:47:26AM -0800, Michael Snyder wrote:
> Elena Zannoni wrote:
> >
> > Sorry, but does this conflict with the extern in gregset.h?
> >
> > extern void fill_fpxregset (gdb_fpxregset_t *fpxregs, int regno);
> >
> > We have gdb_fpxregset_t vs. elf_fpxregset_t.
> >
> > Should we just use one or the other?
> > I just remembered running into a similar problem some time back.
>
> Hmm, well since this is (currently) only used on Linux, we COULD
> just use elf_gregset_t, but I was following a precident that was
> set for gregset_t and fpregset_t, to avoid potential portability
> problems.
>
> The types "gdb_gregset_t" and "gdb_fpregset_t" were introduced
> because there was no consistent definition across platforms for
> gregset and fpregset. Linux uses elf_fpregset, solaris uses
> prfpregset, sunos uses fpregset...
>
> The gregset.h header file defines a portable interface to the
> rest of gdb, which therefore does not need to know what the
> native types of fpregset etc. are.
>
> 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.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-01-10 19:56 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 [this message]
2002-01-10 12:14 ` Kevin Buettner
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=20020110145653.B10383@nevyn.them.org \
--to=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