Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Michael Snyder <msnyder@cygnus.com>
Cc: gdb-patches@sources.redhat.com, drow@mvista.com
Subject: Re: [PATCH] Export fill_fpxregset
Date: Wed, 09 Jan 2002 16:04:00 -0000	[thread overview]
Message-ID: <15420.53104.770587.362588@localhost.cygnus.com> (raw)
In-Reply-To: <200201092228.g09MSGl03285@reddwarf.cygnus.com>


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.

Thanks

Elena


Michael Snyder writes:
 > 2002-01-09  Michael Snyder  <msnyder@redhat.com>
 > 
 > 	* i386-linux-nat.c (fill_fpxregset): Make global.
 > 	(store_fpxregset): Ditto.
 > 
 > Index: i386-linux-nat.c
 > ===================================================================
 > RCS file: /cvs/src/src/gdb/i386-linux-nat.c,v
 > retrieving revision 1.33
 > diff -c -3 -p -r1.33 i386-linux-nat.c
 > *** i386-linux-nat.c	2001/12/27 19:52:31	1.33
 > --- i386-linux-nat.c	2002/01/09 22:25:44
 > ***************
 > *** 1,5 ****
 >   /* Native-dependent code for Linux/x86.
 > !    Copyright 1999, 2000, 2001 Free Software Foundation, Inc.
 >   
 >      This file is part of GDB.
 >   
 > --- 1,5 ----
 >   /* Native-dependent code for Linux/x86.
 > !    Copyright 1999, 2000, 2001, 2002 Free Software Foundation, Inc.
 >   
 >      This file is part of GDB.
 >   
 > *************** static void store_fpregs (int tid, int r
 > *** 452,458 ****
 >   /* Fill GDB's register array with the floating-point and SSE register
 >      values in *FPXREGSETP.  */
 >   
 > ! static void
 >   supply_fpxregset (elf_fpxregset_t *fpxregsetp)
 >   {
 >     i387_supply_fxsave ((char *) fpxregsetp);
 > --- 452,458 ----
 >   /* Fill GDB's register array with the floating-point and SSE register
 >      values in *FPXREGSETP.  */
 >   
 > ! void
 >   supply_fpxregset (elf_fpxregset_t *fpxregsetp)
 >   {
 >     i387_supply_fxsave ((char *) fpxregsetp);
 > *************** supply_fpxregset (elf_fpxregset_t *fpxre
 > *** 462,468 ****
 >      *FPXREGSETP with the value in GDB's register array.  If REGNO is
 >      -1, do this for all registers.  */
 >   
 > ! static void
 >   fill_fpxregset (elf_fpxregset_t *fpxregsetp, int regno)
 >   {
 >     i387_fill_fxsave ((char *) fpxregsetp, regno);
 > --- 462,468 ----
 >      *FPXREGSETP with the value in GDB's register array.  If REGNO is
 >      -1, do this for all registers.  */
 >   
 > ! void
 >   fill_fpxregset (elf_fpxregset_t *fpxregsetp, int regno)
 >   {
 >     i387_fill_fxsave ((char *) fpxregsetp, regno);


  parent reply	other threads:[~2002-01-10  0:04 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 [this message]
2002-01-10 11:52   ` Michael Snyder
2002-01-10 11:56     ` Daniel Jacobowitz
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=15420.53104.770587.362588@localhost.cygnus.com \
    --to=ezannoni@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@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