ro added a comment.
While doing 2-stage builds, the 2 `XFAIL`s due to Bug 42493 were required.
However, I've since also done a 1-stage build with gcc 10, which shows
Unexpectedly Passed Tests (2):
UBSan-Standalone-sparc :: TestCases/Float/cast-overflow.cpp
UBSan-Standalone-sparc :: TestCases/Misc/log-path_test.cpp
which is no wonder since the underlying bug only exists in `clang` `long
double` handling.
I'm a bit uncertain how to deal with this: since the Solaris/sparcv9 buildbot
currently does 1-stage builds with gcc, the resulting `XPASS`es would turn the
bot red. However, currently there's no clang-vs.-gcc feature in `lit` to
distinguish the two builds, AFAICT. `libcxx` has something like this, but that
might be overkill to extract.
Perhaps just remove the `XFAIL`s for now?
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D86621/new/
https://reviews.llvm.org/D86621
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
