From: Daniel Jacobowitz <drow@false.org>
To: Maxim Grigoriev <maxim@tensilica.com>
Cc: gdb-patches@sources.redhat.com,
Bob Wilson <bwilson@tensilica.com>,
Marc Gauthier <marc@tensilica.com>
Subject: Re: Xtensa GDB port -- revised patch
Date: Fri, 10 Nov 2006 20:39:00 -0000 [thread overview]
Message-ID: <20061110203908.GC1115@nevyn.them.org> (raw)
In-Reply-To: <45259B4B.3010101@hq.tensilica.com>
On Thu, Oct 05, 2006 at 04:54:51PM -0700, Maxim Grigoriev wrote:
> Hi Daniel and GDB maintainers,
>
> >>Can you use the previous frame's stack pointer instead?
> >>Is that going to work?
>
> Yes, it works fine.
>
> I've attached a modified patch.
Thanks. This is almost OK. There are a few small issues left:
- The port needs a maintainer, and an entry in MAINTAINERS. Who will
be the maintainer?
- I noticed that your prev_register recursively calls
frame_register_unwind. This isn't a big problem but it is
incorrect. If you defer to another frame, you should set
e.g. realnump to point the number for the next frame. See
trad_frame_get_prev_register for an example.
- There's one stray hunk:
> @@ -1330,7 +1332,6 @@
> done
>
> Makefile: Makefile.in config.status @frags@
> - # Regenerate the Makefile and the tm.h / nm.h links.
> CONFIG_FILES=Makefile \
- There's a few instances of operators without spaces around them,
like "-=4" and "(op1)==0x6c" and "8? 8". I don't think you need to
go back and fix them at this point, but please be careful in the
future.
With the first three things fixed, I think we could commit the patch.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-11-10 20:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 1:07 Maxim Grigoriev
2006-09-28 1:19 ` Daniel Jacobowitz
2006-10-05 23:55 ` Maxim Grigoriev
2006-10-06 9:51 ` Eli Zaretskii
2006-11-10 20:39 ` Daniel Jacobowitz [this message]
2006-11-11 1:21 ` Maxim Grigoriev
2006-11-11 1:40 ` Daniel Jacobowitz
2006-11-11 2:15 ` Maxim Grigoriev
[not found] ` <455530BB.3060403@hq.tensilica.com>
2006-11-14 21:54 ` Daniel Jacobowitz
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=20061110203908.GC1115@nevyn.them.org \
--to=drow@false.org \
--cc=bwilson@tensilica.com \
--cc=gdb-patches@sources.redhat.com \
--cc=marc@tensilica.com \
--cc=maxim@tensilica.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