From: Joel Brobecker <brobecker@adacore.com>
To: Jeff Kenton <jkenton@tilera.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add support for Tilera TILE-Gx processor (part 1/3: gdb)
Date: Mon, 14 May 2012 16:24:00 -0000 [thread overview]
Message-ID: <20120514162412.GJ10253@adacore.com> (raw)
In-Reply-To: <4FAD39A1.1000209@tilera.com>
> gdb/
> * tilegx-linux-tdep.c: New file
> * tilegx-tdep.c: New file
> * configure.host: Add tilegx target.
> * configure.tgt: Add tilegx target.
> * Makefile.in: Add tilegx dependencies.
>
> gdb/regformats/
> * reg-tilegx.dat: New file.
>
> gdb/config/tilegx/
> * nm-linux.h: New file.
There is something I missed as well: I thought you were submitted
both target and native at the same time, but I see now that patch
#2 is taking care of the native part. IN that case, I think that
the configure.host changes are superfluous, and and nm-linux.h also.
These two should be move to patch #2.
Can you resubmit patch #2 & #3 after you've clean them up?
--
Joel
prev parent reply other threads:[~2012-05-14 16:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 16:09 Jeff Kenton
2012-05-14 16:21 ` Joel Brobecker
2012-05-21 14:23 ` Jeff Kenton
2012-05-23 17:34 ` Pedro Alves
2012-05-24 19:26 ` Jeff Kenton
2012-05-25 15:17 ` Pedro Alves
2012-05-29 15:24 ` Jeff Kenton
2012-05-29 17:11 ` Jeff Kenton
2012-05-29 15:24 ` Jeff Kenton
2012-05-30 19:56 ` Pedro Alves
2012-05-30 20:09 ` Jeff Kenton
2012-05-31 8:53 ` [patch] Compilation regression on older gcc + 32-bit host [Re: [PATCH] Add support for Tilera TILE-Gx processor (part 1/3: gdb)] Jan Kratochvil
2012-05-31 10:05 ` Pedro Alves
2012-05-31 15:40 ` [patch] Require long long for GDB [Re: [patch] Compilation regression on older gcc + 32-bit host] Jan Kratochvil
2012-06-01 14:45 ` [commit] Fix tilegx-linux-tdep.c compilation [Re: [patch] Require long long for GDB] Jan Kratochvil
2012-05-14 16:24 ` Joel Brobecker [this message]
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=20120514162412.GJ10253@adacore.com \
--to=brobecker@adacore.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