public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: gdb-patches@sourceware.org
Cc: NIIBE Yutaka <gniibe@fsij.org>,
	Takashi Yoshii <takasi-y@ops.dti.ne.jp>,
	Nobuhiro Iwamatsu <iwamatsu@nigauri.org>,
	j-core@lists.j-core.org, debian-superh@lists.debian.org,
	Linux-sh list <linux-sh@vger.kernel.org>,
	576242@bugs.debian.org
Subject: Re: RFC: Add native support for Linux SH
Date: Fri, 10 Feb 2017 21:06:00 -0000	[thread overview]
Message-ID: <171f95c6-3834-0575-ae17-4c7c511f2b15@physik.fu-berlin.de> (raw)
In-Reply-To: <20170210205546.7982-1-glaubitz@physik.fu-berlin.de>

Forgot to CC some relevant people and lists.

On 02/10/2017 09:55 PM, John Paul Adrian Glaubitz wrote:
> Hi!
> 
> I have picked up an old patch which was posted to this mailing list
> in 2011 [1] which adds native GDB support for Linux SuperH (SH).
> 
> Since this patch was never merged for various reasons, it gained
> dust and needed some work to be usable with current versions of
> GDB again.
> 
> I have taken the patch and forward-ported it to the current version
> of GDB from git master. I have tested it on my SH7785LCR SuperH
> hardware on Debian unstable and I was able to debug simple C
> programs. I have not thoroughly tested the functionality, however.
> 
> With this post, I would like to ask for some feedback on how to
> proceed with this patch. The original author of the patch is
> Takashi Yoshii who wrote it while working at Renesas Electronics
> in Japan.
> 
> Back in 2011, one of the major show-stoppers why the patch was
> not merged was apparently the missing FSF copyright assignment
> by the author [2]. However, since Yoshii-san was working for
> Renesas back then, I think the copyright assignment would have
> to be signed by them and not him personally. And since Renesas
> has already contributed various SuperH code to various FSF
> projects like gcc and binutils, I'd assume that the necessary
> FSF copyright assignment has already been signed.
> 
> I have also asked Yutaka Niibe (CC'ed) to try to get into touch
> with Takashi Yoshii through his old connections at Renesas, in
> case we would need some input from Yoshii-san's side.
> 
> As for the technical part: I'm happy to take any feedback and
> improve the patch so it has reached the necessary quality to
> be able to get merged into GDB mainline.
> 
> Having native GDB support for Linux SH has become relevant
> again since the SuperH architecture is currently being
> redeveloped as the J-Core open source architecture [3].
> 
> Thanks,
> Adrian
> 
>> [1] http://www.cygwin.com/ml/gdb-patches/2011-11/msg00490.html
>> [2] http://www.cygwin.com/ml/gdb-patches/2011-11/msg00499.html
>> [3] http://j-core.org/
> 
> --
>  .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaubitz@debian.org
> `. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
>   `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
> 


-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  parent reply	other threads:[~2017-02-10 21:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10 21:03 John Paul Adrian Glaubitz
2017-02-10 21:03 ` [PATCH] gdb: " John Paul Adrian Glaubitz
2017-02-13 18:57   ` Luis Machado
2017-02-13 18:59     ` John Paul Adrian Glaubitz
2017-02-10 21:06 ` John Paul Adrian Glaubitz [this message]
2017-02-13 22:27 ` RFC: " Yao Qi
2017-02-13 22:31   ` John Paul Adrian Glaubitz
2017-02-16 21:48     ` Yao Qi
2017-02-18 12:32       ` John Paul Adrian Glaubitz
2017-02-18 20:07         ` Yao Qi
2017-03-10 10:50           ` Yao Qi
2017-03-10 10:53             ` John Paul Adrian Glaubitz
2017-06-12 12:15       ` John Paul Adrian Glaubitz
2017-06-12 14:15         ` Yao Qi
2017-02-16 19:02   ` Mike Frysinger
2018-06-21  9:49   ` John Paul Adrian Glaubitz

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=171f95c6-3834-0575-ae17-4c7c511f2b15@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=576242@bugs.debian.org \
    --cc=debian-superh@lists.debian.org \
    --cc=gdb-patches@sourceware.org \
    --cc=gniibe@fsij.org \
    --cc=iwamatsu@nigauri.org \
    --cc=j-core@lists.j-core.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=takasi-y@ops.dti.ne.jp \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).