From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [SH] gdb.arch/gdb1291.exp, gdb.arch/gdb1431.exp
Date: Wed, 28 Mar 2012 04:52:00 -0000 [thread overview]
Message-ID: <20120327215213.232d5857@mesquite.lan> (raw)
In-Reply-To: <87fwcze2w7.fsf@schwinge.name>
On Fri, 23 Mar 2012 16:46:32 +0100
Thomas Schwinge <thomas@codesourcery.com> wrote:
> Exactly the same for gdb.arch/gdb1431.exp: their source files
> (gdb.arch/gdb1291.s, gdb.arch/gdb1431.s) are identical, and I first
> propose to get rid of one of them:
>
> gdb/testsuite/
>
> * gdb.arch/gdb1431.s: Remove file.
> * gdb.arch/gdb1431.exp (srcfile): Refer to gdb1291.s.
I don't know enough about the tests in question to say whether
this is a good approach or not. Is there a chance that someone
will want to tweak the code for one of the test cases without
also having to tweak the other?
Kevin
next prev parent reply other threads:[~2012-03-28 4:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 15:47 Thomas Schwinge
2012-03-28 4:52 ` Kevin Buettner [this message]
2012-03-30 17:58 ` Thomas Schwinge
2012-04-16 7:54 ` Thomas Schwinge
2012-05-09 2:27 ` Thomas Schwinge
2012-05-16 14:11 ` Thomas Schwinge
2012-05-16 14:37 ` Joel Brobecker
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=20120327215213.232d5857@mesquite.lan \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
/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