From: Anthony Green <green@moxielogic.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH: new gdb port: moxie-elf
Date: Fri, 24 Apr 2009 01:02:00 -0000 [thread overview]
Message-ID: <49F10F94.3000107@moxielogic.com> (raw)
In-Reply-To: <20090424000050.GK7552@adacore.com>
Joel Brobecker wrote:
>> 2009-04-23 Anthony Green <green@moxielogic.com>
>> * moxie-tdep.h: New file.
>> * moxie-tdep.c: New file.
>> * configure.tgt: Add moxie-elf.
>>
>
> Looks good to me, after you fix the minor style issues reported below.
> Can you also send a patch announcing this new port in the NEWS file?
> You probably also need to update the MAINTAINERS file in the "Target
> Instruction Set Architectures" section to add your architecture to
> the list. That way, gdb_buildall.sh will pick it up.
>
>
Ok, thanks. I'll do all of that.
> This target compiles with -Werror, right?
>
>
Think so. I'll confirm before I commit.
>> +static CORE_ADDR
>> +moxie_skip_prologue (struct gdbarch *gdbarch, CORE_ADDR pc)
>>
>
> I see that you decided to keep this function implementation as is.
> As long as it works for you, that's fine. I would be a little more
> concerned if this had any repercussions on the core-gdb maintainance,
> but I don't see this as being a potential problem.
>
>
No, I changed this function to use skip_prologue_using_sal()./
>> + /* No function symbol -- just return the PC. */
>>
>
> Just an extra space missing here.
>
>
>> +/* Assuming THIS_FRAME is a dummy, return the frame ID of that dummy
>> + frame. The frame ID's base needs to match the TOS value saved by
>> + save_dummy_frame_tos(), and the PC match the dummy frame's breakpoint. */
>>
>
> This function description should be removed.
>
>
>> +/* moxie register names. */
>>
>
> Missing extra space :)
>
>
I'll fix all of those and post the patch as committed.
Thanks Joel!
AG
next prev parent reply other threads:[~2009-04-24 1:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 11:57 green
2009-04-23 18:29 ` Joel Brobecker
2009-04-23 21:25 ` Anthony Green
2009-04-23 23:41 ` Anthony Green
2009-04-24 0:01 ` Joel Brobecker
2009-04-24 1:02 ` Anthony Green [this message]
2009-04-24 2:27 ` Anthony Green
2009-04-24 3:28 ` Joel Brobecker
2009-05-01 3:20 ` Anthony Green
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=49F10F94.3000107@moxielogic.com \
--to=green@moxielogic.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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