On Mon, Sep 21, 2020 at 10:41:19AM -0700, sunil.k.pandey via Gcc-patches wrote:
> On Linux/x86_64,
> 
> 79f4e20dd1280e6a44736070b0d5213f9a8f85d4 is the first bad commit
> commit 79f4e20dd1280e6a44736070b0d5213f9a8f85d4
> Author: Martin Liska <mli...@suse.cz>
> Date:   Wed Sep 2 14:30:16 2020 +0200
> 
>     Use SIZE_AMOUNT macro for GGC memory allocation numbers.
> 
> caused
> 
> FAIL: g++.dg/ext/timevar2.C  -std=gnu++14 (test for excess errors)
> FAIL: g++.dg/ext/timevar2.C  -std=gnu++98 (test for excess errors)

We should also prune N% from the output, I think.

Ok for trunk?  Tested by running timevar2.C a couple of dozen times.

        * g++.dg/ext/timevar2.C: Also prune N%.
---
 gcc/testsuite/g++.dg/ext/timevar2.C | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gcc/testsuite/g++.dg/ext/timevar2.C 
b/gcc/testsuite/g++.dg/ext/timevar2.C
index 46c3e1b4794..7d3f1218314 100644
--- a/gcc/testsuite/g++.dg/ext/timevar2.C
+++ b/gcc/testsuite/g++.dg/ext/timevar2.C
@@ -4,6 +4,7 @@
 // { dg-prune-output "k" }
 // { dg-prune-output " 0 " }
 // { dg-prune-output "checks" }
+// { dg-prune-output "\[0-9\]+%" }
 
 namespace detail {
 namespace indirect_traits {}

base-commit: 762c16eba6b815090c56564a293cd059aea2e1d6
-- 
2.26.2

Reply via email to