Eric f376a3bba1 Work around GCC test failure that is caused by enabling optimizations. (#73998) ...

While trying to work around MSAN/TSAN build timeouts, we enabled
optimizations on some tests. This caused GCC to start complaining that
some values may be uninitialized. I believe GCC is wrong, but more
investigation is needed.

The values are initialized when the variable `__g` is either < 0 or >=
0. Which only leaves out NaN I believe, which is likely well into UB
   land anyway.

However, more investigation needed.

2023-12-03 00:43:41 -05:00

..

append_range.pass.cpp

…

assign_range.pass.cpp

…

clear.pass.cpp

…

emplace_back.pass.cpp

…

emplace_front.pass.cpp

…

emplace.pass.cpp

…

erase_iter_iter.invalidation.pass.cpp

…

erase_iter_iter.pass.cpp

…

erase_iter.invalidation.pass.cpp

…

erase_iter.pass.cpp

…

insert_iter_initializer_list.pass.cpp

…

insert_iter_iter.pass.cpp

Work around GCC test failure that is caused by enabling optimizations. (#73998)

2023-12-03 00:43:41 -05:00

insert_range.pass.cpp

…

insert_rvalue.pass.cpp

…

insert_size_value.pass.cpp

…

insert_value.pass.cpp

…

pop_back.invalidation.pass.cpp

…

pop_back.pass.cpp

…

pop_front.invalidation.pass.cpp

…

pop_front.pass.cpp

…

prepend_range.pass.cpp

…

push_back_exception_safety.pass.cpp

…

push_back_rvalue.pass.cpp

…

push_back.pass.cpp

…

push_front_exception_safety.pass.cpp

…

push_front_rvalue.pass.cpp

…

push_front.pass.cpp

…