Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com,
	ezannoni <ezannoni@sources.redhat.com>,
	"vinschen >> Corinna Vinschen" <vinschen@redhat.com>
Subject: Re: [RFA] Improvements for sh double register display
Date: Tue, 15 Jul 2003 22:34:00 -0000	[thread overview]
Message-ID: <3F148155.9010602@redhat.com> (raw)
In-Reply-To: <16148.21516.843971.449438@localhost.redhat.com>

Elena Zannoni wrote:
> Michael Snyder writes:
>  > 2003-07-02  Michael Snyder  <msnyder@redhat.com>
>  > 
>  > 	* sh-tdep.c (do_dr_register_info): Fix register number output
>  > 	(0, 2, 4, ... not 0, 1, 2...).  Display DP register both in
>  > 	hex and in floating point (noting when it is not valid FP).
>  > 
>  > Index: sh-tdep.c
>  > ===================================================================
>  > RCS file: /cvs/src/src/gdb/sh-tdep.c,v
>  > retrieving revision 1.132
>  > diff -p -r1.132 sh-tdep.c
>  > *** sh-tdep.c	13 Jun 2003 04:40:34 -0000	1.132
>  > --- sh-tdep.c	2 Jul 2003 18:00:22 -0000
>  > *************** static void
>  > *** 3928,3938 ****
>  >   do_dr_register_info (int dr_regnum)
>  >   {
>  >     int first_fp_reg_num = dr_reg_base_num (dr_regnum);
>  >   
>  > !   printf_filtered ("dr%d\t0x%08x%08x\n", 
>  > ! 		    dr_regnum - gdbarch_tdep (current_gdbarch)->DR0_REGNUM, 
>  > ! 		    (int) read_register (first_fp_reg_num),
>  > ! 		    (int) read_register (first_fp_reg_num + 1));
>  >   }
>  >   
>  >   /* Double precision registers, compact mode. */
>  > --- 3928,3962 ----
>  >   do_dr_register_info (int dr_regnum)
>  >   {
>  >     int first_fp_reg_num = dr_reg_base_num (dr_regnum);
>  > +   char *raw_buffer;
>  > +   double dbl;
>  > +   int inv;
>  >   
>  > !   /* Allocate space for the float. */
>  > !   raw_buffer = (char *) alloca (2 * REGISTER_RAW_SIZE (FP0_REGNUM));
> 
> Can you use something other than alloca here? Also, this will collide
> in mid air with Corinna's revamp. Maybe you can revisit this after she
> is done? Otherwise it's ok.

OK, I'll touch space-helmets with Corinna.
BTW, what's wrong with alloca?



  parent reply	other threads:[~2003-07-15 22:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02 18:01 Michael Snyder
2003-07-15 19:13 ` Elena Zannoni
2003-07-15 19:56   ` Andrew Cagney
2003-07-15 22:35     ` Michael Snyder
2003-07-16  2:33       ` Andrew Cagney
2003-07-15 22:34   ` Michael Snyder [this message]
2003-07-16  9:51     ` Corinna Vinschen

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=3F148155.9010602@redhat.com \
    --to=msnyder@redhat.com \
    --cc=ezannoni@redhat.com \
    --cc=ezannoni@sources.redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vinschen@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