|
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 |
|
| #
8f8d5f00 |
| 17-Oct-2024 |
Chris Apple <cja-private@pm.me> |
[rtsan] Add statistics for suppression count (#112718)
|
| #
1efa6625 |
| 16-Oct-2024 |
Chris Apple <cja-private@pm.me> |
[rtsan] Introduce function-name-matches suppression (#112108)
Introduces a new type of suppression:
1. function-name-matches - allows users to disable `malloc`, `free`,
`pthread_mutex_lock` or s
[rtsan] Introduce function-name-matches suppression (#112108)
Introduces a new type of suppression:
1. function-name-matches - allows users to disable `malloc`, `free`,
`pthread_mutex_lock` or similar. This could be helpful if a user thinks
these are real-time safe on their OS. Also allows disabling of any
function marked [[blocking]].
This is useful as a **more performant "early outs" compared to the
`call-stack-contains` suppression**. `call-stack-contains` is inherently
VERY costly, needing to inspect every frame of every stack for a
matching string. This new suppression has an early out before we unwind
the stack.
show more ...
|
|
Revision tags: llvmorg-19.1.2 |
|
| #
4468d580 |
| 12-Oct-2024 |
Chris Apple <cja-private@pm.me> |
[rtsan] Support basic call stack suppressions (#111608)
This adds basic support for suppressions, which is a first class feature
of the other sanitizers.
|
| #
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.
|
| #
10d43061 |
| 07-Oct-2024 |
Chris Apple <cja-private@pm.me> |
[rtsan][NFC] Refactor to scoped bypasser for __rtsan::Context (#111438)
|
|
Revision tags: llvmorg-19.1.1 |
|
| #
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 ...
|
| #
ce0c41cb |
| 21-Sep-2024 |
davidtrevelyan <davidtrevelyan@users.noreply.github.com> |
[rtsan][NFC] Move assertions and diagnostics into own impl files (#109500)
In preparation for providing more information to rtsan's diagnostics
output (via `__rtsan_expect_not_realtime`), this PR s
[rtsan][NFC] Move assertions and diagnostics into own impl files (#109500)
In preparation for providing more information to rtsan's diagnostics
output (via `__rtsan_expect_not_realtime`), this PR separates out all
logic for i) making rtsan's assertions about real-time context state and
ii) displaying diagnostics to the user - disentangling them both from
the rtsan `Context`.
We'll follow up this PR with a simplification to the unit tests that
reflect this new separation.
show more ...
|