public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: binutils@sourceware.org
Subject: Re: Fix testsuite XPASSes
Date: Sat, 14 May 2011 00:52:00 -0000	[thread overview]
Message-ID: <20110514005216.GA20800@bubble.grove.modra.org> (raw)
In-Reply-To: <20110513041419.GB30815@bubble.grove.modra.org>

On Fri, May 13, 2011 at 01:44:20PM +0930, Alan Modra wrote:
> This cures some XPASSes.  In the case of the gas redef2 and redef3
> tests, certain targets will now FAIL that silently XFAILed before.  If
> my analysis is correct these new FAILs are real failures: performing a
> final link on the object file resulted in a binary with wrong
> addresses.

Oops, didn't mean to make x64_64-mingw fail.

	* gas/all/gas.exp: Fix typo last change.

Index: gas/testsuite/gas/all/gas.exp
===================================================================
RCS file: /cvs/src/src/gas/testsuite/gas/all/gas.exp,v
retrieving revision 1.73
diff -u -p -r1.73 gas.exp
--- gas/testsuite/gas/all/gas.exp	13 May 2011 04:16:22 -0000	1.73
+++ gas/testsuite/gas/all/gas.exp	13 May 2011 16:12:25 -0000
@@ -145,7 +145,7 @@ case $target_triplet in {
 	# failures such as or32-elf.
 	setup_xfail "bfin-*-*" "i\[3-7\]86-*-*coff" \
 	    "i\[3-7\]86-*-*pe" "i\[3-7\]86-*-go32*" \
-	    "i\[3-7\]86-*-cygwin*" "i\[3-7\]86-*-mingw*" "86_64-*-mingw*"
+	    "i\[3-7\]86-*-cygwin*" "i\[3-7\]86-*-mingw*" "x86_64-*-mingw*"
 	run_dump_test redef3
 	gas_test_error "redef4.s" "" ".set for symbol already used as label"
 	gas_test_error "redef5.s" "" ".set for symbol already defined through .comm"

-- 
Alan Modra
Australia Development Lab, IBM

      reply	other threads:[~2011-05-14  0:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-13  4:14 Alan Modra
2011-05-14  0:52 ` Alan Modra [this message]

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=20110514005216.GA20800@bubble.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).