Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: kevinb@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfc] mn10300: Add am33 support
Date: Sat, 03 Sep 2005 10:03:00 -0000	[thread overview]
Message-ID: <200509031003.j83A3UQ2009709@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20050902183118.05e24025@ironwood.lan> (message from Kevin Buettner on Fri, 2 Sep 2005 18:31:18 -0700)

> Date: Fri, 2 Sep 2005 18:31:18 -0700
> From: Kevin Buettner <kevinb@redhat.com>
> 
> The following patch adds am33 support to mn10300-tdep.c.
> 
> This code has various authors.  I believe that Andrew Cagney, Jackie
> Smith Cashion, Alex Oliva, and myself all had a hand in writing bits
> of it.  All of the above authors are (or were at the time the code was
> written) covered by Red Hat's copyright assignment.
> 
> Comments?
> 
> 	* mn10300-tdep.c (am33_2_register_name): New function.
> 	(my_frame_is_in_sp, my_frame_is_in_fp, my_frame_is_last)
> 	(set_my_stack_size): Delete.
> 	(set_movm_offsets, set_reg_offsets): Rename the former to the
> 	latter.  Update for handling am33.
> 	(mn10300_analyze_prologue): Update for handling am33.  Also, make
> 	minor improvements in quality of prologue analysis.
> 	(mn10300_gdbarch_init):  Add am33 support.
> 	* mn10300-tdep.h (E_NUM_REGS): Delete.
> 

Please use safe_frame_unwind_memory instead of
deprecated_read_memory_nobpt.  Otherwise this looks ok.

Cheers,

Mark


  reply	other threads:[~2005-09-03 10:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-03  1:31 Kevin Buettner
2005-09-03 10:03 ` Mark Kettenis [this message]
2005-09-06 22:34   ` Kevin Buettner
2005-09-08 22:50     ` Kevin Buettner
2005-09-07  3:39 ` Michael Snyder

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=200509031003.j83A3UQ2009709@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --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