On Mon, Nov 17, 2025 at 09:41:50PM +0100, Jakub Jelinek wrote:
> On Mon, Nov 17, 2025 at 03:17:07PM -0500, Marek Polacek wrote:
> > > --- gcc/testsuite/g++.dg/debug/pr94459.C.jj 2020-04-05
> > > 00:27:46.554215583 +0200
> > > +++ gcc/testsuite/g++.dg/debug/pr94459.C 2025-11-15 22:25:24.364486317
> > > +0100
> > > @@ -1,6 +1,6 @@
> > > // PR debug/94459
> > > // { dg-do compile { target c++14 } }
> > > -// { dg-options "-g -dA" }
> > > +// { dg-options "-g -dA -std=gnu++17" }
> >
> > Does this change make sense, given the dg-do compile above?
>
> Clearly it does work, as debug.exp doesn't cycle over C++ versions but over
> various different debug options. The c++14 effective target isn't that
Ah, that explains it.
> important, but if it stays, it documents the test needs at least C++14.
> Could be also { target { c++14 && c++17_down } } but we'd still
> need -std=gnu++17 explicitly to fix the test.
Fair enough, it appeared strange that the target seemed to imply "run
in C++14 and up" but we would always use gnu++17. All good then.
Marek
