From: Richard Earnshaw <rearnsha@arm.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: PING 3: [patch, testsuite] General ARM target triplet
Date: Wed, 19 Jan 2011 18:24:00 -0000 [thread overview]
Message-ID: <1295458009.26870.2.camel@e102346-lin.cambridge.arm.com> (raw)
In-Reply-To: <4D370C8E.8010307@codesourcery.com>
On Wed, 2011-01-19 at 09:08 -0700, Yao Qi wrote:
> On 01/13/2011 04:47 AM, Yao Qi wrote:
> > On 01/06/2011 08:10 AM, Yao Qi wrote:
> >> On 12/13/2010 11:39 PM, Pedro Alves wrote:
> >>>>> OK, I combine them together in one single patch this time.
> >>> Thanks. If/when everyone's happy with the triplet bits
> >>> proper, this is okay.
> >>
> >> Ping. Are you happy with this triplet? :-)
> >>
> >> http://sourceware.org/ml/gdb-patches/2010-12/msg00187.html
> >>
> >
> > Ping.
> >
>
> Ping again with a small fix pointed out by Matthew. Richard, are you OK
> with that?
>
> --
> Yao Qi
+proc dwarf2_support {} {
+ if {![istarget *-*-linux*]
+ && ![istarget *-*-gnu*]
+ && ![istarget *-*-elf*]
+ && ![istarget *-*-openbsd*]
+ && ![istarget arm*-*-eabi*]
+ && ![istarget arm*-*-symbianelf*]
+ && ![istarget powerpc-*-eabi*]} {
+ return 0
+ }
+
+ return 1
+}
Why is this negated? It would seem more sensible to me to have a list
of supported targets that returns 1 and then default to returning 0 for
everything else. Why? Because then if the list gets too long its
easier to add a second cluster in an independent if-clause.
The ARM bits are all fine. The dwarf2 changes look generally sensible,
but should be reviewed by a full gdb maintainer, which I'm not.
R.
next prev parent reply other threads:[~2011-01-19 17:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 16:33 Yao Qi
2010-12-03 17:00 ` Joseph S. Myers
2010-12-03 17:36 ` Richard Earnshaw
2010-12-03 18:05 ` Joseph S. Myers
2010-12-03 18:06 ` Richard Earnshaw
2010-12-05 9:20 ` Yao Qi
2010-12-05 9:39 ` Andreas Schwab
2010-12-05 12:43 ` Yao Qi
2010-12-13 14:07 ` Pedro Alves
2010-12-13 15:29 ` Yao Qi
2010-12-13 15:39 ` Pedro Alves
2010-12-20 6:34 ` Yao Qi
2011-01-06 14:11 ` PING: " Yao Qi
2011-01-13 11:52 ` PING 2: " Yao Qi
2011-01-19 16:15 ` PING 3: " Yao Qi
2011-01-19 18:24 ` Richard Earnshaw [this message]
2011-01-19 19:03 ` Ulrich Weigand
2011-01-19 20:43 ` Yao Qi
2011-01-13 14:53 ` PING: " Matthew Gretton-Dann
2011-01-13 15:16 ` Yao Qi
2010-12-05 12:15 ` Yao Qi
2010-12-13 3:52 ` Ping: " Yao Qi
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=1295458009.26870.2.camel@e102346-lin.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).