Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <luisgpm@linux.vnet.ibm.com>
To: gdb-patches@sourceware.org
Subject: [ob][PATCH] ppc32: Make atomic instruction testcase failure quiet.
Date: Sat, 17 May 2008 13:53:00 -0000	[thread overview]
Message-ID: <1210972000.1733.34.camel@gargoyle> (raw)

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

Hi,

This should be obvious enough. ppc32 doesn't support the atomic
instructions tested by this testcase and it shows expected compiler
errors. This patch makes those messages go away.

Regards,
Luis


[-- Attachment #2: clean-atomic-test.diff --]
[-- Type: text/x-patch, Size: 965 bytes --]

2008-04-16  Luis Machado  <luisgpm@br.ibm.com>

	* gdb.arch/ppc64-atomic-inst.exp: Make the expected compile failure
	quiet for ppc32 and group options into a single variable.

Index: testsuite/gdb.arch/ppc64-atomic-inst.exp
===================================================================
--- testsuite.orig/gdb.arch/ppc64-atomic-inst.exp	2008-05-16 17:52:09.000000000 -0300
+++ testsuite/gdb.arch/ppc64-atomic-inst.exp	2008-05-16 17:56:50.000000000 -0300
@@ -35,9 +35,9 @@
 set testfile "ppc64-atomic-inst"
 set srcfile ${testfile}.c
 set binfile ${objdir}/${subdir}/${testfile}
-set compile_flags "debug"
+set compile_flags "debug quiet"
 
-if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable [concat debug additional_flags=-m64]] != "" } {
+if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable [concat $compile_flags additional_flags=-m64]] != "" } {
     unsupported "Testcase compile failed."
     return -1
 }

             reply	other threads:[~2008-05-16 21:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-17 13:53 Luis Machado [this message]
2008-05-27 18:43 ` Luis Machado

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=1210972000.1733.34.camel@gargoyle \
    --to=luisgpm@linux.vnet.ibm.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