From: Tristan Gingold <gingold@adacore.com>
To: binutils <binutils@sourceware.org>
Subject: [Patch] Fix some testsuite regressions for alpha vms
Date: Mon, 18 Apr 2011 12:40:00 -0000 [thread overview]
Message-ID: <C299A05E-238D-48BE-A99B-BB723EACF9F9@adacore.com> (raw)
Hi,
this patch fixes 13 regressions (due to unusual section names for .text/.data/.bss) and kills one test for alpha vms.
Ok for trunk ?
Tristan.
gas/testsuite
2011-04-18 Tristan Gingold <gingold@adacore.com>
* lib/gas-defs.exp (get_standard_section_names): Add names for
alpha vms.
* gas/all/gas.exp: Do not test diff1.s on alpha-vms.
diff --git a/gas/testsuite/gas/all/gas.exp b/gas/testsuite/gas/all/gas.exp
index 59500a1..c7cc452 100644
--- a/gas/testsuite/gas/all/gas.exp
+++ b/gas/testsuite/gas/all/gas.exp
@@ -34,12 +34,14 @@ if { ![istarget cris-*-*] && ![istarget crisv32-*-*]
# This test is meaningless for the PA; the difference of two undefined
# symbols is something that is (and must be) supported on the PA.
+# The same is true for alpha-vms
#
# The MN10300 port supports link time relaxation which in turn allows
# for link time resolution of the differneces of two symbols which are
# undefined at assembly time. Hence this test will not pass for the
# MN10300. The same thing is true for the RX port as well.
if { ![istarget hppa*-*-*]
+ && ![istarget alpha*-*-*vms*]
&& ![istarget rx-*-*]
&& ![istarget mn10300-*-*]
&& ![istarget am3*-*-*] } then {
diff --git a/gas/testsuite/lib/gas-defs.exp b/gas/testsuite/lib/gas-defs.exp
index f10d72a..9d89a2e 100644
--- a/gas/testsuite/lib/gas-defs.exp
+++ b/gas/testsuite/lib/gas-defs.exp
@@ -290,6 +290,10 @@ proc get_standard_section_names {} {
if [istarget "rx-*-*"] {
return { "P" "D_1" "B_1" }
}
+ if [istarget "alpha*-*-*vms*"] {
+ # Double quote: for TCL and for sh.
+ return { "\\\$CODE\\\$" "\\\$DATA\\\$" "\\\$BSS\\\$" }
+ }
return
}
next reply other threads:[~2011-04-18 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 12:40 Tristan Gingold [this message]
2011-04-18 13:34 ` Nick Clifton
2011-04-18 13:44 ` Tristan Gingold
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=C299A05E-238D-48BE-A99B-BB723EACF9F9@adacore.com \
--to=gingold@adacore.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).