From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Kevin Buettner <kevinb@cygnus.com>,
Elena Zannoni <ezannoni@cygnus.com>,
gdb@sources.redhat.com
Subject: Re: What's the correct type for {supply,fill}_fpregset?
Date: Mon, 19 Nov 2001 13:36:00 -0000 [thread overview]
Message-ID: <3C04908B.2090605@cygnus.com> (raw)
In-Reply-To: <1011120174021.ZM18927@ocotillo.lan>
>> The defintions in use are from ppc-linux-nat.c:
>> void fill_fpregset (gdb_fpregset_t *fpregsetp, int regno)
>> void supply_fpregset (gdb_fpregset_t * fpregsetp)
>>
>> Or should the calls in thread-db.c be changed?
>
>
> This has frequently been a source of annoyance for me and I had never
> really taken a close look to see how things ought to be done...
>
> It seems to me that reason for {supply,fill}_[fp,g}regset()'s existence
> is to 1) communicate with /proc on Solaris, Unixware, and AIX5 systems
> and 2) to communicate with the thread library.
DanielJ, did you recently hit this problem with, er, MIPS? Something
about trying to fix it but getting a patch bounced?
Andrew
WARNING: multiple messages have this Message-ID
From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Kevin Buettner <kevinb@cygnus.com>,
Elena Zannoni <ezannoni@cygnus.com>,
gdb@sources.redhat.com
Subject: Re: What's the correct type for {supply,fill}_fpregset?
Date: Tue, 27 Nov 2001 23:53:00 -0000 [thread overview]
Message-ID: <3C04908B.2090605@cygnus.com> (raw)
Message-ID: <20011127235300.vKUfIW2lc-ly6QxS5NGG99AOD9zAu3JzrQvC8OqABUc@z> (raw)
In-Reply-To: <1011120174021.ZM18927@ocotillo.lan>
>> The defintions in use are from ppc-linux-nat.c:
>> void fill_fpregset (gdb_fpregset_t *fpregsetp, int regno)
>> void supply_fpregset (gdb_fpregset_t * fpregsetp)
>>
>> Or should the calls in thread-db.c be changed?
>
>
> This has frequently been a source of annoyance for me and I had never
> really taken a close look to see how things ought to be done...
>
> It seems to me that reason for {supply,fill}_[fp,g}regset()'s existence
> is to 1) communicate with /proc on Solaris, Unixware, and AIX5 systems
> and 2) to communicate with the thread library.
DanielJ, did you recently hit this problem with, er, MIPS? Something
about trying to fix it but getting a patch bounced?
Andrew
next prev parent reply other threads:[~2001-11-28 7:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-08 19:15 Elena Zannoni
2001-11-09 2:05 ` Kevin Buettner
2001-11-19 13:36 ` Andrew Cagney [this message]
2001-11-27 23:27 ` Daniel Jacobowitz
2001-11-19 8:35 ` Daniel Jacobowitz
2001-11-27 23:53 ` Andrew Cagney
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=3C04908B.2090605@cygnus.com \
--to=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=ezannoni@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@cygnus.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