diff options
| author | Alexandre Oliva <oliva@adacore.com> | 2022-06-23 23:20:51 -0300 |
|---|---|---|
| committer | Alexandre Oliva <oliva@gnu.org> | 2022-06-23 23:28:14 -0300 |
| commit | f01cf5eaa06e72cf8e1e7d7f37b41f9d5eaf3e5c (patch) | |
| tree | 3dc19aee0ee866270c1748306006ffbe4062bd51 /gcc/d/expr.cc | |
| parent | b931c6874e846cd4eba1c31112593d33ff4bf1f1 (diff) | |
| download | gcc-f01cf5eaa06e72cf8e1e7d7f37b41f9d5eaf3e5c.zip gcc-f01cf5eaa06e72cf8e1e7d7f37b41f9d5eaf3e5c.tar.gz gcc-f01cf5eaa06e72cf8e1e7d7f37b41f9d5eaf3e5c.tar.bz2 | |
libstdc++: testsuite: skip fs last_write_time tests if dummy
The last_write_time functions are defined in ways that are useful, or
that fail immediately, depending on various macros. When they fail
immediately, the filesystem last_write_time.cc tests fail noisily, but
the fail is entirely expected.
Define NO_LAST_WRITE_TIME in the last_write_time.cc tests, according
to the macros that select implementations of last_write_time, and use
it through the new dg-require-target-fs-lwt to skip tests that are
expected to fail.
for libstdc++-v3/ChangeLog
* testsuite/util/testsuite_fs.h (NO_LAST_WRITE_TIME): Define
when appropriate.
* testsuite/lib/libstdc++.exp
(check_v3_target_fs_last_write_time): New.
* testsuite/lib/dg-options.exp (dg-require-target-fs-lwt):
New.
* testsuite/27_io/filesystem/operations/last_write_time.cc:
Skip the test if the features are unavailable.
* testsuite/experimental/filesystem/operations/last_write_time.cc:
Likewise.
Diffstat (limited to 'gcc/d/expr.cc')
0 files changed, 0 insertions, 0 deletions