DavidSpickett added a comment. > Wasn't sure how to properly test this since the original reproducer > technically relies on implementation-defined behaviour (i.e., initialising a > bitfield with an out-of-range value). Suggestions are welcome
Is this undefined behaviour defined at least for clang only across platforms? I'm guessing most of the time the test suite programs are built with clang, though you can change that with a cmake var. Perhaps you could do something like `@skipifnotclang` in that case. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D134493/new/ https://reviews.llvm.org/D134493 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits