Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "J. Johnston" <jjohnstn@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: modernization of ia64-tdep.c with new frame model for gdb-6.0 branch
Date: Mon, 25 Aug 2003 23:29:00 -0000	[thread overview]
Message-ID: <3F4A9BDA.9030706@redhat.com> (raw)
In-Reply-To: <1030825184133.ZM9803@localhost.localdomain>

Kevin Buettner wrote:
> On Aug 25,  2:12pm, J. Johnston wrote:
> 
> 
>>Kevin Buettner wrote:
> 
> 
>>>Okay, I see that you're turning r32-r127 and (not shown) p0-p64
>>>into pseudo registers.  Is there any reason to leave big "holes"
>>>in the register number space?  I.e, why not just get rid of all
>>>of the empty strings above?
>>>
>>>(Most of the time, the reason NOT to do this is because remote
>>>targets depend on the order.  The only remote target that I'm
>>>aware of is gdbserver, and I'm not particularly worried about
>>>breaking compatibility.)
>>>
>>>If I'm not mistaken, removing these holes will somewhat decrease
>>>the size of struct ia64_frame_cache:
>>>
>>>    +struct ia64_frame_cache
>>>    +{
>>>    ...
>>>    +  /* Saved registers.  */
>>>    +  CORE_ADDR saved_regs[NUM_IA64_RAW_REGS];
>>>    +
>>>    +};
>>>
>>
>>Actually, number of real raw registers went down to the last non-pseudo
>>register anyway.  My preference regarding renumbering registers would be
>>to sync this up with gdbserver later.
> 
> 
> Okay, so long as "later" isn't too much later.  It'd be a shame if someone
> suddenly wrote a stub which depended on the holes being there...
> 
> 
>>>Have you tested the nat bit related code in ia64_pseudo_register_read()
>>>and ia64_pseudo_register_write() ?  My recollection is that my original
>>>code didn't handle the unat bits correctly.  I was wondering if you
>>>had fixed this problem.  (I'm curious about the other NaT bits too.)
>>>
>>
>>Could you elaborate about what problems you think existed in the previous
>>code?
> 
> 
> I'll send you a thread which describes the problems.  After rereading
> that thread, it looks like the fix isn't as difficult as I had
> remembered.  In fact, it should be pretty easy.  (But it still needs
> to be tested.)
> 
> With regard to your current patch, I'm okay with you checking it in
> after adding the ia64_frame_cache comments.
> 
> Thanks for doing these cleanups.
> 
> Kevin
> 

Thanks Kevin.  Patch is checked in with comments added.

-- Jeff J.


  reply	other threads:[~2003-08-25 23:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30 20:54 J. Johnston
2003-07-31 19:03 ` J. Johnston
2003-07-31 19:20   ` Daniel Jacobowitz
2003-07-31 21:39     ` J. Johnston
2003-08-08 17:32 ` J. Johnston
2003-08-22 21:46   ` Kevin Buettner
2003-08-25 18:12     ` J. Johnston
2003-08-25 18:41       ` Kevin Buettner
2003-08-25 23:29         ` J. Johnston [this message]
2003-08-08 17:49 Michael Elizabeth Chastain
2003-08-08 18:57 ` J. Johnston

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=3F4A9BDA.9030706@redhat.com \
    --to=jjohnstn@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@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