Thanks for your prompt feedback on this Jonathan.

> On 18 Dec 2020, at 23:24, Jonathan Wakely <jwak...@redhat.com> wrote:
> 
>> Is this ok to commit ?
> 
> Yes, OK, although I wonder if this would be better:
> 
> { dg-prune-output "/(functional|bits/invoke.h):" }

Probably more robust, I agree. This still works
both with build tree (tested on mainline) and install
tree (tested on our gcc-10 branch).

Same ChangeLog.

Olivier

From fe8db9fe481fe705400b1366a8709f7048418c7f Mon Sep 17 00:00:00 2001
From: Olivier Hainque <hain...@adacore.com>
Date: Fri, 18 Dec 2020 18:09:21 +0000
Subject: [PATCH] Tweak dg-prune-output regex for out-of-tree contexts

libstdc++-v3/

        * testsuite/20_util/bind/ref_neg.cc: Tweak the
        dg-prune-output regex for out-of-build-tree contexts.
---
 libstdc++-v3/testsuite/20_util/bind/ref_neg.cc | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/20_util/bind/ref_neg.cc 
b/libstdc++-v3/testsuite/20_util/bind/ref_neg.cc
index d77ad90cc253..cc392b63a466 100644
--- a/libstdc++-v3/testsuite/20_util/bind/ref_neg.cc
+++ b/libstdc++-v3/testsuite/20_util/bind/ref_neg.cc
@@ -49,7 +49,8 @@ void test02()
 }
 
 // Ignore the reasons for deduction/substitution failure in the headers.
-// { dg-prune-output "/include/(functional|bits/invoke.h):" }
+// Arrange for the match to work on installed trees as well as build trees.
+// { dg-prune-output "/(functional|bits/invoke.h):" }
 
 int main()
 {
-- 
2.17.1




Reply via email to