Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Jeff Kenton <jkenton@tilera.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Add support for Tilera TILE-Gx processor (part 1/2: gdb)
Date: Fri, 20 Apr 2012 01:58:00 -0000	[thread overview]
Message-ID: <4F90B188.30809@codesourcery.com> (raw)
In-Reply-To: <4F906647.8090303@tilera.com>

Jeff,
Thanks for adding a new port tilegx in GDB.

For each patch, it needs a ChangeLog entry, so your patch part 1/2 and
2/2 needs one ChangeLog entry respectively.  Read this if it helps

  http://www.gnu.org/prep/standards/html_node/Change-Logs.html

You also need to provide a patch to gdb/NEWS to mention this new port.

 * New targets

 Renesas RL78                    rl78-*-elf
 HP OpenVMS ia64                 ia64-hp-openvms*

You can add tilegx in this way.

Do you have FSF copyright assignment?  If you don't have, someone here
can help you to get that done.

On 04/20/2012 03:23 AM, Jeff Kenton wrote:
> @@ -723,7 +724,7 @@
>         regcache.c reggroups.c remote.c remote-fileio.c reverse.c \
>         sentinel-frame.c \
>         serial.c ser-base.c ser-unix.c skip.c \
> -       solib.c solib-target.c source.c \
> +       solib-target.c source.c \
>         stabsread.c stack.c std-regs.c symfile.c symfile-mem.c symmisc.c \
>         symtab.c \
>         target.c target-descriptions.c target-memory.c \
> @@ -905,7 +906,7 @@
>         reggroups.o regset.o \
>         trad-frame.o \
>         tramp-frame.o \
> -       solib.o solib-target.o \
> +       solib-target.o \
>         prologue-value.o memory-map.o memrange.o \
>         xml-support.o xml-syscall.o xml-utils.o \
>         target-descriptions.o target-memory.o xml-tdesc.o xml-builtin.o \

Why do you remove solib.c and solib.o?

-- 
Yao (齐尧)


  reply	other threads:[~2012-04-20  0:44 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19 19:26 Jeff Kenton
2012-04-20  1:58 ` Yao Qi [this message]
2012-04-20 12:54 ` Joel Brobecker
2012-04-20 14:03   ` Jeff Kenton
2012-04-21  0:34     ` Joel Brobecker
2012-04-23 19:59   ` Jeff Kenton
2012-04-24 16:07     ` Pedro Alves
2012-04-24 16:07     ` Pedro Alves
2012-04-24 16:07     ` Pedro Alves
2012-04-24 16:07     ` Pedro Alves
2012-04-24 16:08     ` Pedro Alves
2012-04-24 16:11     ` Pedro Alves
2012-04-24 16:14     ` Pedro Alves
2012-04-24 16:22     ` Pedro Alves
2012-04-24 18:47       ` Jeff Kenton
2012-04-24 20:21       ` Jeff Kenton
2012-04-24 22:40         ` Pedro Alves
2012-04-24 16:23     ` Pedro Alves
2012-04-24 16:27     ` Pedro Alves
2012-04-24 16:38     ` Pedro Alves
2012-04-24 16:40     ` Pedro Alves
2012-04-24 16:41       ` Pedro Alves
2012-04-24 16:41     ` Pedro Alves
2012-04-24 16:59       ` Jeff Kenton
2012-04-24 16:42     ` Pedro Alves
2012-04-24 16:54     ` Pedro Alves
2012-04-25  2:18     ` Yao Qi
2012-04-23 20:12   ` [PATCH] Add support for Tilera TILE-Gx processor (part 2/2: gdbserver) Jeff Kenton
2012-04-24 16:54     ` Pedro Alves
2012-04-24 16:55     ` Pedro Alves
2012-04-24 17:34     ` Pedro Alves
2012-05-03 14:28       ` Jeff Kenton
2012-05-03 14:44         ` Pedro Alves

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=4F90B188.30809@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jkenton@tilera.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