Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: "J. Johnston" <jjohnstn@redhat.com>
Cc: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: RFA: ia64 tdep patch
Date: Thu, 23 Oct 2003 17:46:00 -0000	[thread overview]
Message-ID: <1031023174642.ZM14291@localhost.localdomain> (raw)
In-Reply-To: "J. Johnston" <jjohnstn@redhat.com> "Re: RFA: ia64 tdep patch" (Oct 23, 12:22pm)

On Oct 23, 12:22pm, J. Johnston wrote:

> I have included a patch which contains responses to your comments thus far.
> 
> The ChangeLog is:
> 
> 2003-10-23  Jeff Johnston  <jjohnstn@redhat.com>
> 	* ia64-tdep.c: (ia64_frame_cache): Add new prev_cfm field.
> 	(pseudo_regs): Add comment regarding register stack registers.
> 	(ia64_alloc_frame_cache):  Initialize new prev_cfm field to 0.
> 	(floatformat_valid): New static routine.
> 	(floatformat_ia64_ext): Add name field and set up is_valid routine
> 	to floatformat_valid().
> 	(examine_prologue):  For the previous cfm, use
> 	frame_unwind_register()
> 	if the cfm is not stored in a register-stack register.  Save the
> 	previous cfm value in the prev_cfm field.  Add debug output.
> 	(ia64_frame_this_id): Use frame_id_build_special() to also register
> 	the bsp.  Add debug output.
> 	(ia64_sigtramp_frame_this_id): Ditto.
> 	(ia64_frame_prev_register):  Look at cache saved_regs for a few more
> 	registers and also add some checks for framelessness before accepting
> 	current register values for fields such as return address.  For cfm,
> 	use the cached prev_cfm field if available.  Add comment to explain
> 	PSR logic.  Add debug output.
> 	(ia64_sigtramp_frame_init_saved_regs): Bump up base by 16 to get
> 	sp needed for calling lower level
> 	ia64_linux_sigcontext_register_address().  Also save the
> 	bsp and sp address as part of initialization.
> 	(ia64_sigtramp_frame_cache): Hard-code stack size as it can't be
> 	calculated.  Cache the bsp and cfm values.
> 	(ia64_sigtramp_frame_prev_register): Add logic to this routine out
> 	instead of using ia64_frame_prev_register() which doesn't expect most
> 	registers to be saved.  The saved values for bsp and sp
> 	can be taken from the cache.  Add debug output.
> 	(ia64_push_dummy_call): Use frame_id_build_special() to also register
> 	the bsp.
> 
> Ok?

Okay.

Kevin


  reply	other threads:[~2003-10-23 17:46 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
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 [this message]
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=1031023174642.ZM14291@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