aboutsummaryrefslogtreecommitdiff
path: root/gcc/value-range.h
diff options
context:
space:
mode:
authorJakub Jelinek <jakub@redhat.com>2022-09-23 09:46:59 +0200
committerJakub Jelinek <jakub@redhat.com>2022-09-23 09:47:32 +0200
commita0de11d0d22054b6fd76a0730a3ec807542379d0 (patch)
tree9467132f5afa2afa319bb1f56ae3f0ddb7192706 /gcc/value-range.h
parent2ec6489d7a595c78cae4584244afd4ca91d6c8ff (diff)
downloadgcc-a0de11d0d22054b6fd76a0730a3ec807542379d0.zip
gcc-a0de11d0d22054b6fd76a0730a3ec807542379d0.tar.gz
gcc-a0de11d0d22054b6fd76a0730a3ec807542379d0.tar.bz2
testsuite: Fix up pr106922.C test
On Thu, Sep 22, 2022 at 01:10:08PM +0200, Richard Biener via Gcc-patches wrote: > * g++.dg/tree-ssa/pr106922.C: Adjust. > --- a/gcc/testsuite/g++.dg/tree-ssa/pr106922.C > +++ b/gcc/testsuite/g++.dg/tree-ssa/pr106922.C > @@ -87,5 +87,4 @@ void testfunctionfoo() { > } > } > > -// { dg-final { scan-tree-dump-times "Found fully redundant value" 4 "pre" { xfail { ! lp64 } } } } > -// { dg-final { scan-tree-dump-not "m_initialized" "cddce3" { xfail { ! lp64 } } } } > +// { dg-final { scan-tree-dump-not "m_initialized" "dce3" } } I've noticed +UNRESOLVED: g++.dg/tree-ssa/pr106922.C -std=gnu++20 scan-tree-dump-not dce3 "m_initialized" +UNRESOLVED: g++.dg/tree-ssa/pr106922.C -std=gnu++2b scan-tree-dump-not dce3 "m_initialized" with this change, both on x86_64 and i686. The dump is still cddce3, additionally as the last reference to the pre dump is gone, not sure it is worth creating that dump. With the following patch, there aren't FAILs nor UNRESOLVED tests with GXX_TESTSUITE_STDS=98,11,14,17,20,2b make check-g++ RUNTESTFLAGS="--target_board=unix\{-m32,-m64\} dg.exp='pr106922.C'" 2022-09-23 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/106922 * g++.dg/tree-ssa/pr106922.C: Scan in cddce3 dump rather than dce3. Remove -fdump-tree-pre-details from dg-options.
Diffstat (limited to 'gcc/value-range.h')
0 files changed, 0 insertions, 0 deletions