diff options
author | Martin Storsjö <martin@martin.st> | 2023-11-02 09:51:33 +0200 |
---|---|---|
committer | Martin Storsjö <martin@martin.st> | 2023-11-03 11:30:08 +0200 |
commit | e9db60c05e2fb96ff40cbb1f78790abc5de9237e (patch) | |
tree | 5327889e59d50c829f57799197691ae5a155caf3 /llvm/lib/Bitcode/Reader/BitcodeReader.cpp | |
parent | 060de415af335fdd82910f409e2be3b8457eaa43 (diff) | |
download | llvm-e9db60c05e2fb96ff40cbb1f78790abc5de9237e.zip llvm-e9db60c05e2fb96ff40cbb1f78790abc5de9237e.tar.gz llvm-e9db60c05e2fb96ff40cbb1f78790abc5de9237e.tar.bz2 |
Reapply [clang-repl] [test] Make an XFAIL more precise (#70991)
The const.cpp testcase fails when running in MSVC mode, while it does
succeed in MinGW mode.
In MSVC mode, there are more constructor invocations than expected, as
the printout looks like this:
A(1), this = 0000025597930000
A(1), this = 0000025597930000
f: this = 0000025597930000, val = 1
A(1), this = 0000025597930000
f: this = 0000025597930000, val = 1
~A, this = 0000025597930000, val = 1
~A, this = 0000025597930000, val = 1
~A, this = 0000025597930000, val = 1
While the expected printout looks like this:
A(1), this = 000002C903E10000
f: this = 000002C903E10000, val = 1
f: this = 000002C903E10000, val = 1
~A, this = 000002C903E10000, val = 1
Reapplying with the XFAIL pattern expanded to include PS4/PS5
triples as well, which also seem to have the same behaviour
as MSVC.
Diffstat (limited to 'llvm/lib/Bitcode/Reader/BitcodeReader.cpp')
0 files changed, 0 insertions, 0 deletions