Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Thu, 19 Mar 2009 13:59:00 -0000	[thread overview]
Message-ID: <20090319135606.GB583@adacore.com> (raw)
In-Reply-To: <OF9A757A5E.036ADC13-ON4825757E.002528EB-4825757E.0027F1AE@sunplusct.com>

Just for the record: I just sent Don a private message asking if
Qinwei could approve the S+core part or not. So I will not address
this part.

> --- src/gdb/configure.tgt	2009-03-16 23:04:14.000000000 +0800
> +++ src.mod/gdb/configure.tgt	2009-03-17 09:26:44.000000000 +0800
> @@ -375,7 +375,11 @@
>  
>  score-*-*)
>  	# Target: S+core embedded system
> -	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
>  	;;
>  
>  sh*-*-linux*)


Regarding this change, I am 50-50, leaning towards accepting it.

    Cons: There is no score simulator and you are not planning on
          contributing it. So, it is a useless change as far as the FSF
          is concerned. As such, I don't see why we should accept it.
          Maintaining small local changes in your own tree is very easy.

    Pros: I can't see any.

That being said, the reason why I'm split on this is that it wouldn't
cost us much to accept the change. I don't see how it could cause
any trouble.

GDB Global Maintainers:

Do we have a policy on this sort of change?

-- 
Joel


  reply	other threads:[~2009-03-19 13:56 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
2009-03-19  7:36   ` don.lee
2009-03-19 13:59     ` Joel Brobecker [this message]
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=20090319135606.GB583@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