diff options
| author | Thurston Dang <thurston@google.com> | 2024-11-26 14:58:44 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-11-26 14:58:44 -0800 |
| commit | 47dbf359041299c5f19f82e7204c6c9675b6e69a (patch) | |
| tree | 6438dc4767aeb8b5c0ee7bd084150c48e27b8c1e /llvm/lib/Bitcode/Writer/BitcodeWriterPass.cpp | |
| parent | 39601a6e5484de183bf525b7d0624e7890ccd8ab (diff) | |
| download | llvm-47dbf359041299c5f19f82e7204c6c9675b6e69a.zip llvm-47dbf359041299c5f19f82e7204c6c9675b6e69a.tar.gz llvm-47dbf359041299c5f19f82e7204c6c9675b6e69a.tar.bz2 | |
Reapply "[NFC][clang] Add ubsan-trap-merge.c test to show absence of nomerge" (#117804) (#117805)
This reverts commit c8bdb31ff66e8934060c60816c57925fdec42a2c.
It was reverted because I forgot to update the auto-generated assertions
after adding the target triple.
Original commit message:
This test (copied from https://github.com/llvm/llvm-project/pull/83470)
demonstrates that UBSan does not add the nomerge annotation. This is
significant because it can result in them being merged by the backend,
even when -ubsan-unique-traps is enabled.
N.B. https://github.com/llvm/llvm-project/pull/65972 (continuation of
https://reviews.llvm.org/D148654) had considered adding nomerge to
ubsantrap, but did not proceed with that because of
https://github.com/llvm/llvm-project/issues/53011.
https://github.com/llvm/llvm-project/pull/101549 fixed that limitation
("It sets nomerge flag for the node if the instruction has nomerge
arrtibute."); planned upcoming work
(https://github.com/llvm/llvm-project/pull/117651) will add nomerge for
ubsan.
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriterPass.cpp')
0 files changed, 0 insertions, 0 deletions