From patchwork Thu Sep  8 03:09:38 2011
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: [cxx-mem-model] Call torture-finish in testing infrastructure
Date: Wed, 07 Sep 2011 17:09:38 -0000
From: Aldy Hernandez <aldyh@redhat.com>
X-Patchwork-Id: 113860
Message-Id: <4E6831F2.4050603@redhat.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>, Andrew MacLeod <amacleod@redhat.com>

Apparently, if you don't call torture-finish, subsequent tests in dg.exp 
inherit CFLAGS incorrectly.  Serves me right for not testing the entire 
testsuite when making changes to memmodel.exp.  When will I learn to 
expect the unexpected when making seemingly unrelated changes...?

Committed to branch.
* gcc.dg/memmodel/memmodel.exp: Call torture-finish.
        * g++.dg/memmodel/memmodel.exp: Likewise.


Index: gcc.dg/memmodel/memmodel.exp
===================================================================
--- gcc.dg/memmodel/memmodel.exp	(revision 178607)
+++ gcc.dg/memmodel/memmodel.exp	(working copy)
@@ -54,4 +54,5 @@ if [info exists guality_gdb_name] {
     unsetenv GUALITY_GDB_NAME
 }
 
+torture-finish
 dg-finish
Index: g++.dg/memmodel/memmodel.exp
===================================================================
--- g++.dg/memmodel/memmodel.exp	(revision 178607)
+++ g++.dg/memmodel/memmodel.exp	(working copy)
@@ -54,4 +54,5 @@ if [info exists guality_gdb_name] {
     unsetenv GUALITY_GDB_NAME
 }
 
+torture-finish
 dg-finish