[PATCH] Avoid spurious test failures when -fno-inline in test flags

Jonathan Wakely jwakely@redhat.com
Fri Jan 4 18:56:00 GMT 2019


On 04/01/19 11:38 +0000, Jonathan Wakely wrote:
>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.

And another similar patch.

Tested x86_64-linux, committed to trunk.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch.txt
Type: text/x-patch
Size: 1116 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20190104/a072a0f9/attachment.bin>


More information about the Libstdc++ mailing list