This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Why do we { dg-require-debug-mode "" } for tests not using it?

From: François Dumont <frs dot dumont at gmail dot com>
To: Jonathan Wakely <jwakely at redhat dot com>, libstdc++ at gcc dot gnu dot org
Date: Tue, 10 Jan 2017 22:23:32 +0100
Subject: Re: Why do we { dg-require-debug-mode "" } for tests not using it?
Authentication-results: sourceware.org; auth=none
References: <20170110174635.GO13348@redhat.com>

On 10/01/2017 18:46, Jonathan Wakely wrote:

We have a number of tests like
testsuite/21_strings/debug/self_move_assign_neg.cc which use:

// { dg-require-debug-mode "" }

But then they #include <debug/string> and test __gnu_debug::string
which is always available (not just in Debug Mode).

Is there some reason for this?

I can't see any. Maybe some historical directive, has ever std::stringDebug mode been activated with _GLIBCXX_DEBUG macro ?

According ChangeLog it is this way since introduction of this test caseback in 2012.


François

References:
- Why do we { dg-require-debug-mode "" } for tests not using it?
  - From: Jonathan Wakely

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]