Avoid spurious test failures when -fno-inline in test flags
authorJonathan Wakely <jwakely@redhat.com>
Fri, 4 Jan 2019 11:06:49 +0000 (11:06 +0000)
committerJonathan Wakely <redi@gcc.gnu.org>
Fri, 4 Jan 2019 11:06:49 +0000 (11:06 +0000)
commit5db78cac104c0427b023b3a21f98bf302aa736e3
tree1aa8cf0cfa86b0e9b326bd8b1ac68a8d3be4f54e
parenta52fcfac0a9621e4ee5345272873d96f55ad3d18
Avoid spurious test failures when -fno-inline in test flags

These tests rely on inlining, so if -fno-inline is added to the compiler
flags the tests fail. Use the predefined __NO_INLINE__ macro to detect
that situation, and don't bother testing the move assignment.

* testsuite/21_strings/basic_string/modifiers/assign/char/
move_assign_optim.cc: Avoid spurious failure when -fno-inline added
to test flags.
* testsuite/21_strings/basic_string/modifiers/assign/wchar_t/
move_assign_optim.cc: Likewise.

From-SVN: r267573
libstdc++-v3/ChangeLog
libstdc++-v3/testsuite/21_strings/basic_string/modifiers/assign/char/move_assign_optim.cc
libstdc++-v3/testsuite/21_strings/basic_string/modifiers/assign/wchar_t/move_assign_optim.cc