llvm-project Mini-Update#4348
Conversation
…put.ascii.pass.cpp` to `libcxx/test/libcxx`.
…throw_exception.pass.cpp` for MSVC's STL.
…FLAGS(cl-style-warnings)`. (`alg.find/find.pass.cpp` already has one.)
…nother `XFAIL: msvc` test.
It's probably the same bug as DevCom-10439137 "Discarded id-expression causes unnecessary reading". |
|
Yep, I agree! Great catch, I didn't know about that bug report. I've updated the entry. I also noted in VSO-1869865 (the internal mirror of DevCom-10439137) that the ICE I just reduced, VSO-1948221 "x86chk ICE with |
|
I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed. |
|
I had to push an additional commit because new tests appeared that require Unix headers, and the MSVC-internal test harness doesn't understand this. |
|
Should |
|
@cpplearner That's a good idea. We already have Since the PR and its mirror have passed checks, I'll explore doing this the next time I update LLVM. Thanks! |
I started by adding a script
check_libcxx_paths.pyto make LLVM updates easier. Then I figured I'd see how easy it was, and it only took me a day instead of a month.llvm/llvm-project#79793 is still in flight, but the affected test is blocked by a suspected MSVC compiler bug with
constexpr, so we don't need to wait.