|
Revision tags: llvmorg-21-init, llvmorg-19.1.7, llvmorg-19.1.6, llvmorg-19.1.5, llvmorg-19.1.4, llvmorg-19.1.3, llvmorg-19.1.2 |
|
| #
3423a5e3 |
| 08-Oct-2024 |
Chris Apple <cja-private@pm.me> |
[rtsan][NFC] Refactor where we unwind the stack (#111443)
This change alters where we unwind the stack. We now do it in ExpectNotRealtime, and pass in the DiagnosticInfo and Stack to OnViolation.
|
|
Revision tags: llvmorg-19.1.1 |
|
| #
e069434a |
| 27-Sep-2024 |
Chris Apple <cja-private@pm.me> |
[rtsan][NFC] Remove unncessary namespace specifiers (#110197)
|
| #
a04db2c7 |
| 21-Sep-2024 |
davidtrevelyan <davidtrevelyan@users.noreply.github.com> |
[rtsan] Decouple assertions from error actions (#109535)
Decouples sanitizer assertion `ExpectNotRealtime` from the action that
should happen if a real-time context is detected.
|
| #
1b601938 |
| 21-Sep-2024 |
Chris Apple <cja-private@pm.me> |
[rtsan][compiler-rt] Introduce __rtsan_notify_blocking_call (#109529)
# Why?
In llvm, we need to add a call to `__rtsan_notify_blocking_call()` when
a function is marked `[[clang::blocking]]`. T
[rtsan][compiler-rt] Introduce __rtsan_notify_blocking_call (#109529)
# Why?
In llvm, we need to add a call to `__rtsan_notify_blocking_call()` when
a function is marked `[[clang::blocking]]`. This will produce a
different error message than a call to an unsafe malloc etc
show more ...
|
| #
cf85b33e |
| 21-Sep-2024 |
davidtrevelyan <davidtrevelyan@users.noreply.github.com> |
[rtsan] Prune rtsan context and assertions tests (#109503)
Disentangles (and simplifies) integration-like tests for
`__rtsan::ExpectNotRealtime` and `__rtsan::Context` into simpler unit
tests. Non
[rtsan] Prune rtsan context and assertions tests (#109503)
Disentangles (and simplifies) integration-like tests for
`__rtsan::ExpectNotRealtime` and `__rtsan::Context` into simpler unit
tests. None of the tests are new, but their assertions have changed to
reflect the more direct testing strategy.
show more ...
|