Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: "J. Johnston" <jjohnstn@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: RFA: ia64 tdep patch
Date: Mon, 20 Oct 2003 20:13:00 -0000	[thread overview]
Message-ID: <1031020201315.ZM20659@localhost.localdomain> (raw)
In-Reply-To: "J. Johnston" <jjohnstn@redhat.com> "RFA: ia64 tdep patch" (Oct 17,  3:58pm)

On Oct 17,  3:58pm, J. Johnston wrote:

> The attached ia64 patch fixes a few problems, most notably
> backtracing through signal handlers.

I think these changes are mostly okay, but...

In your ChangeLog entry, you say:

> 	* ia64-tdep.c: Change all references of DEPRECATED_REGISTER_RAW_SIZE
> 	to use register_size() instead.

Yet, later on, in the patch, I see that you're reintroducing a use of
DEPRECATED_REGISTER_RAW_SIZE:

  +  else if (regnum == IA64_BR0_REGNUM)
  +    {
  +      CORE_ADDR br0 = 0;
  +      CORE_ADDR addr = cache->saved_regs[IA64_BR0_REGNUM];
  +      if (addr != 0)
  +	{
  +	  *lvalp = lval_memory;
  +	  *addrp = addr;
  +	  read_memory (addr, buf, DEPRECATED_REGISTER_RAW_SIZE (IA64_BR0_REGNUM));
  +	  br0 = extract_unsigned_integer (buf, 8);
  +	}
  +      store_unsigned_integer (valuep, 8, br0);
  +    }

Also, regarding:

       /* We want to calculate the previous bsp as the end of the previous register stack frame.
 	 This corresponds to what the hardware bsp register will be if we pop the frame
 	 back which is why we might have been called.  We know the beginning of the current
-         frame is cache->bsp - cache->sof.  This value in the previous frame points to
+	 frame is cache->bsp - cache->sof.  This value in the previous frame points to
 	 the start of the output registers.  We can calculate the end of that frame by adding
 	 the size of output (sof (size of frame) - sol (size of locals)).  */
       ia64_frame_prev_register (next_frame, this_cache, IA64_CFM_REGNUM,
 				&cfm_optim, &cfm_lval, &cfm_addr, &cfm_realnum, cfm_valuep);
       prev_cfm = extract_unsigned_integer (cfm_valuep, 8);
-
+      
       bsp = rse_address_add (cache->bsp, -(cache->sof));
       prev_bsp = rse_address_add (bsp, (prev_cfm & 0x7f) - ((prev_cfm >> 7) & 0x7f));
-
+      

The first white space change is okay, but the latter two are not.  I'd
really prefer to see whitespace changes occur via a separate patch anyway.

So, if you don't mind, could you please submit separate patches for:

  1) whitespace changes
  2) DEPRECATED_... elimination
  3) the CFM / backtracing changes.

Patches (1) and (2) are preapproved -- just make sure that you don't
introduce extra white space on an otherwise blank line.  For (1) and
(2), please post the patches that you end up committing.

Once (1) and (2) are split out, I'd like another chance to review what's
left (patch 3).

With regard to (3), one of the questions that I already have concerns
the following line in ia64_sigtramp_frame_init_saved_regs():

+      CORE_ADDR sp = cache->base + 16;

Could you explain what this is about?  (Preferably with a comment in the
code?)

Thanks,

Kevin

P.S. If you'd prefer to reverse things and submit patch 3 first, that'd
be okay too.


  reply	other threads:[~2003-10-20 20:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-17 19:58 J. Johnston
2003-10-20 20:13 ` Kevin Buettner [this message]
2003-10-20 21:55   ` J. Johnston
2003-10-21 22:22     ` Kevin Buettner
2003-10-21 23:03       ` J. Johnston
2003-10-22 19:38         ` Kevin Buettner
2003-10-22 20:57           ` J. Johnston
2003-10-22 22:01             ` J. Johnston
2003-10-23 16:22               ` J. Johnston
2003-10-23 17:46                 ` Kevin Buettner
2003-10-23 22:07                   ` J. Johnston
2003-10-22 22:03             ` Marcel Moolenaar
2003-10-23 21:01               ` Kevin Buettner
2003-10-23 23:23                 ` Marcel Moolenaar
2003-10-24  4:30                   ` Kevin Buettner
2003-10-24  5:40                     ` Marcel Moolenaar
2003-10-24  7:08                       ` 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=1031020201315.ZM20659@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jjohnstn@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