Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sandra Loosemore <sandra@codesourcery.com>
To: <gdb-patches@sourceware.org>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: [patch, testsuite] restrict gdb.arch/ppc64-symtab-cordic.exp to ppc64 targets
Date: Wed, 29 Jul 2015 22:48:00 -0000	[thread overview]
Message-ID: <55B957AA.6060506@codesourcery.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 234 bytes --]

I've found that it doesn't do anything useful to try loading a ppc64 .ko 
file when testing GDB on ARM, Nios II, etc.  I copied the target test 
logic from the other gdb.arch/ppc64-*.exp testcase -- is this OK to 
check in?

-Sandra


[-- Attachment #2: gdb-cordic.log --]
[-- Type: text/x-log, Size: 137 bytes --]

2015-07-29  Sandra Loosemore  <sandra@codesourcery.com>

	gdb/testsuite/
	* gdb.arch/ppc64-symtab-cordic.exp: Restrict to ppc64 targets.

[-- Attachment #3: gdb-cordic.patch --]
[-- Type: text/x-patch, Size: 614 bytes --]

diff --git a/gdb/testsuite/gdb.arch/ppc64-symtab-cordic.exp b/gdb/testsuite/gdb.arch/ppc64-symtab-cordic.exp
index d9a3f13..fa82510 100644
--- a/gdb/testsuite/gdb.arch/ppc64-symtab-cordic.exp
+++ b/gdb/testsuite/gdb.arch/ppc64-symtab-cordic.exp
@@ -13,6 +13,11 @@
 # You should have received a copy of the GNU General Public License
 # along with this program.  If not, see <http://www.gnu.org/licenses/>.
 
+if {![istarget "powerpc*"] || ![is_lp64_target]} {
+    verbose "Skipping powerpc64 separate debug file symtab test."
+    return
+}
+
 standard_testfile
 
 set kobz2file ${srcdir}/${subdir}/cordic.ko.bz2

             reply	other threads:[~2015-07-29 22:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 22:48 Sandra Loosemore [this message]
2015-07-30 11:33 ` Yao Qi
2015-07-30 11:59 ` Jan Kratochvil

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=55B957AA.6060506@codesourcery.com \
    --to=sandra@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.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