Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Yao Qi <yao@codesourcery.com>,
	Andreas Schwab <schwab@linux-m68k.org>,
	Richard Earnshaw <rearnsha@arm.com>,
	"Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: [patch, testsuite] General ARM target triplet
Date: Mon, 13 Dec 2010 15:39:00 -0000	[thread overview]
Message-ID: <201012131539.22392.pedro@codesourcery.com> (raw)
In-Reply-To: <4D063BA8.4000404@codesourcery.com>

On Monday 13 December 2010 15:28:40, Yao Qi wrote:
> On 12/13/2010 10:07 PM, Pedro Alves wrote:
> >> The second sentence is removed by this (2nd) patch, which depends on the
> >> first patch.
> > 
> > I think it would have been easier if you had just posted this as
> > an updated version of the first patch.
> > 
> 
> 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.

> 
> >> diff --git a/gdb/testsuite/gdb.python/py-section-script.exp b/gdb/testsuite/gdb.python/py-section-script.exp
> >> index 434dca4..373c450 100644
> >> --- a/gdb/testsuite/gdb.python/py-section-script.exp
> >> +++ b/gdb/testsuite/gdb.python/py-section-script.exp
> >> @@ -17,7 +17,6 @@
> >>  # scripts specified in the .debug_gdb_scripts section.
> >>  
> >>  # This test can only be run on targets which support ELF and use gas.
> >> -# For now pick a sampling of likely targets.
> >>  if {![istarget *-*-linux*]
> >>      && ![istarget *-*-gnu*]
> >>      && ![istarget *-*-elf*]
> > 
> > If the "support ELF" comment is correct (as opposed to "support DWARF-2" in
> > the other cases), then you should not remove this one.
> > 
> 
> Done.
> 
> > Back in the first patch:
> > 
> > On Sunday 05 December 2010 12:15:09, Yao Qi wrote:
> >> +# This test can only be run on targets which support DWARF-2 and use gas.
> >> +proc dwarf2_support {} {
> > 
> > There's no "This test" anymore.  Maybe:
> > 
> > # Return true if the target supports DWARF-2 and uses gas.
> > # For now pick a sampling of likely targets.
> 
> Fixed.
> 
> 


-- 
Pedro Alves


  reply	other threads:[~2010-12-13 15:39 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 [this message]
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
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=201012131539.22392.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=joseph@codesourcery.com \
    --cc=rearnsha@arm.com \
    --cc=schwab@linux-m68k.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