From: Dominik Vogt <vogt@linux.vnet.ibm.com>
To: libffi-discuss@sourceware.org
Subject: [PATCH 5/7] Merge of gcc patches
Date: Tue, 18 Nov 2014 10:20:00 -0000 [thread overview]
Message-ID: <20141118101957.GF26714@linux.vnet.ibm.com> (raw)
In-Reply-To: <20141118101743.GA26714@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 64 bytes --]
Patch 5.
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
IBM Germany
[-- Attachment #2: 0005-ChangeLog --]
[-- Type: text/plain, Size: 156 bytes --]
ChangeLog
2014-07-04 Thomas Schwinge <thomas@codesourcery.com>
* testsuite/lib/libffi.exp (libffi-dg-runtest): Change interface
match to dg-runtest's.
[-- Attachment #3: 0005-Normalize-interface-for-all-dg-runtest.patch --]
[-- Type: text/x-diff, Size: 1265 bytes --]
From 824a9fb6e11a03bb24d583336da99be10e008738 Mon Sep 17 00:00:00 2001
From: tschwinge <tschwinge@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Fri, 4 Jul 2014 05:28:17 +0000
Subject: [PATCH 5/7] Normalize interface for all *-dg-runtest.
---
testsuite/lib/libffi.exp | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/testsuite/lib/libffi.exp b/testsuite/lib/libffi.exp
index b1dd1fa..da4e878 100644
--- a/testsuite/lib/libffi.exp
+++ b/testsuite/lib/libffi.exp
@@ -251,7 +251,7 @@ proc search_for { file pattern } {
# Modified dg-runtest that can cycle through a list of optimization options
# as c-torture does.
-proc libffi-dg-runtest { testcases default-extra-flags } {
+proc libffi-dg-runtest { testcases flags default-extra-flags } {
global runtests
foreach test $testcases {
@@ -272,9 +272,9 @@ proc libffi-dg-runtest { testcases default-extra-flags } {
set nshort [file tail [file dirname $test]]/[file tail $test]
- foreach flags $option_list {
- verbose "Testing $nshort, $flags" 1
- dg-test $test $flags ${default-extra-flags}
+ foreach flags_t $option_list {
+ verbose "Testing $nshort, $flags $flags_t" 1
+ dg-test $test "$flags $flags_t" ${default-extra-flags}
}
}
}
--
1.8.4.2
next prev parent reply other threads:[~2014-11-18 10:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 10:17 [PATCH 0/7] " Dominik Vogt
2014-11-18 10:18 ` [PATCH 2/7] " Dominik Vogt
2014-11-18 10:34 ` Richard Henderson
2014-11-18 10:18 ` [PATCH 1/7] " Dominik Vogt
2014-11-18 10:33 ` Richard Henderson
2014-11-18 13:13 ` Richard Henderson
2014-11-18 10:19 ` [PATCH 3/7] " Dominik Vogt
2014-11-18 10:40 ` Richard Henderson
2014-11-18 10:19 ` [PATCH 4/7] " Dominik Vogt
2014-11-18 10:41 ` Richard Henderson
2014-11-18 10:20 ` Dominik Vogt [this message]
2014-11-18 10:42 ` [PATCH 5/7] " Richard Henderson
2014-11-18 10:20 ` [PATCH 6/7] " Dominik Vogt
2014-11-18 10:36 ` Richard Henderson
2014-11-18 11:06 ` Dominik Vogt
2014-11-18 11:34 ` Richard Henderson
2014-11-18 11:57 ` Dominik Vogt
2014-11-18 10:21 ` [PATCH 7/7] " Dominik Vogt
2014-11-18 10:37 ` Richard Henderson
2014-11-18 10:32 ` [PATCH 0/7] " Richard Henderson
2014-11-18 10:47 ` Richard Henderson
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=20141118101957.GF26714@linux.vnet.ibm.com \
--to=vogt@linux.vnet.ibm.com \
--cc=libffi-discuss@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).