From: Joel Brobecker <brobecker@adacore.com>
To: don.lee@sunplusct.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Support new target S+core 3, a variant of S+core
Date: Tue, 17 Mar 2009 16:12:00 -0000 [thread overview]
Message-ID: <20090317155743.GA31979@adacore.com> (raw)
In-Reply-To: <OFF2760387.B9E13E9A-ON4825757C.000A56D3-4825757C.000A9146@sunplusct.com>
> The S+core team in our company have ported GDB to S+core 3, a variant
> of S+core, now we want to contribute some patch. So here it is (see
> attachment).
Thanks, Don.
> Please review it, and any suggestions are most welcome.
Note that Qinwei is also capable of reviewing your code.
I can take a look, but it's better if Qinwei does it, because he has
actual knowledge of the target.
> At now, I'm quite new to GDB, so if you fond something I did wrong,
> please point it out.
If you haven't done so, the gdb/CONTRIBUTE file contains valuable
information. You may also want to give gdb/MAINTAINERS a quick read.
The first thing that struck me was the fact that the patch was produced
in the wrong format, so "context" is missing. Could you resubmit your
patch using the "-u" option? For instance "cvs diff -u ...".
Also, it looks like you are submitting several changes in one patch,
which we prefer not to. For instance, your change to gdb/configure.tgt
can be submitted as is, as it is independent of the target; it just
tells gdb about the the simulator.
> --- src/gdb/MAINTAINERS 2009-03-04 10:26:35.000000000 +0800
> +++ src.mod/gdb/MAINTAINERS 2009-03-04 10:29:15.000000000 +0800
> @@ -307,6 +307,7 @@
>
> score --target=score-elf
> Qinwei qinwei@sunnorth.com.cn
> + Don Lee don.lee@sunplusct.com
>
> sh --target=sh-elf ,-Werror
> --target=sh64-elf ,-Werror
As I said on the gdb@ mailing-list, I would prefer to hold off on
that change, but others might have a different opinion. In any case,
this is also an independent change, so this can be submitted separately
from the rest.
> Index: gdb/configure.tgt
> ===================================================================
> RCS file: /cvs/src/src/gdb/configure.tgt,v
> retrieving revision 1.213
> diff -r1.213 configure.tgt
> 378c378,382
> < gdb_target_obs="score-tdep.o"
> ---
> > gdb_target_obs="score-tdep.o corelow.o"
> > if test -f ../sim/score/Makefile; then
> > gdb_sim=../sim/score/libsim.a
> > fi
> > build_gdbserver=yes
There is no score subdirectory in sim/. Are you going to submit
a simulator for that target?
The rest of the patch is very hard to read! Could you explain a little
bit the actual changes you made? At first sight, what the patch says
is that you replaced pretty much everything, which I doubt is the case.
--
Joel
next prev parent reply other threads:[~2009-03-17 15:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 2:17 don.lee
2009-03-17 16:12 ` Joel Brobecker [this message]
2009-03-19 7:36 ` don.lee
2009-03-19 13:59 ` Joel Brobecker
2009-03-20 2:37 ` Eli Zaretskii
2009-03-20 10:59 ` don.lee
2009-03-20 15:02 ` Eli Zaretskii
[not found] ` <OF51713D49.22E58C13-ON4825757F.00065D83-4825757F.000703CE@sunplusct.com>
2009-03-24 20:33 ` Joel Brobecker
[not found] ` <OF8D1ED069.1AB0D24B-ON48257586.0008306A-48257586.000B6BC2@sunplusct.com>
2009-03-30 15:17 ` Joel Brobecker
[not found] <OFDAF6A5BC.66B4412D-ON48257582.00087E06-48257582.00096DDA@sunplusct.com>
2009-03-23 4:28 ` Eli Zaretskii
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=20090317155743.GA31979@adacore.com \
--to=brobecker@adacore.com \
--cc=don.lee@sunplusct.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