On Fri, Mar 23, 2018 at 01:45:01PM -0300, Alexandre Oliva wrote: > On Mar 23, 2018, Jakub Jelinek <ja...@redhat.com> wrote: > > > On Wed, Mar 21, 2018 at 11:52:33PM -0400, Jason Merrill wrote: > >> OK, thanks. > > > Note the testcase FAILs with -fconcepts when I do make check-c++-all, > > Hmm, I don't get that with check or check-g++. Should we expand the > default std_list in g++-dg.exp, or should I manually test these > additional variants?
I think we should add the -std=c++17 mode to the list of standards cycled by default, now that it is a released standard. -fconcepts is experimental and so is -std=c++2a, so perhaps those can stay out of the default and be just checked occassionally. The full set of check-c++-all FAILs I'm getting that don't show up with check-g++ is: FAIL: g++.dg/spellcheck-macro-ordering-2.C -std=c++17 -fconcepts (test for errors, line 10) FAIL: g++.dg/spellcheck-macro-ordering-2.C -std=c++17 -fconcepts (test for excess errors) FAIL: g++.dg/spellcheck-macro-ordering.C -std=c++17 -fconcepts (test for errors, line 6) FAIL: g++.dg/spellcheck-macro-ordering.C -std=c++17 -fconcepts (test for warnings, line 6) FAIL: g++.dg/spellcheck-macro-ordering.C -std=c++17 -fconcepts (test for warnings, line 15) FAIL: g++.dg/spellcheck-macro-ordering.C -std=c++17 -fconcepts (test for excess errors) FAIL: g++.dg/template/pr84789.C -std=c++17 -fconcepts (test for errors, line 12) FAIL: g++.dg/template/pr84789.C -std=c++17 -fconcepts (test for excess errors) FAIL: g++.dg/warn/string1.C -std=gnu++17 (test for excess errors) FAIL: g++.dg/warn/string1.C -std=gnu++2a (test for excess errors) FAIL: g++.dg/warn/string1.C -std=gnu++17 -fconcepts (test for excess errors) Jakub