core/
ub_checks.rs

1//! Provides the [`assert_unsafe_precondition`] macro as well as some utility functions that cover
2//! common preconditions.
3
4use crate::intrinsics::{self, const_eval_select};
5
6/// Checks that the preconditions of an unsafe function are followed.
7///
8/// The check is enabled at runtime if debug assertions are enabled when the
9/// caller is monomorphized. In const-eval/Miri checks implemented with this
10/// macro for language UB are always ignored.
11///
12/// This macro should be called as
13/// `assert_unsafe_precondition!(check_{library,language}_ub, "message", (ident: type = expr, ident: type = expr) => check_expr)`
14/// where each `expr` will be evaluated and passed in as function argument `ident: type`. Then all
15/// those arguments are passed to a function with the body `check_expr`.
16/// Pick `check_language_ub` when this is guarding a violation of language UB, i.e., immediate UB
17/// according to the Rust Abstract Machine. Pick `check_library_ub` when this is guarding a violation
18/// of a documented library precondition that does not *immediately* lead to language UB.
19///
20/// If `check_library_ub` is used but the check is actually guarding language UB, the check will
21/// slow down const-eval/Miri and we'll get the panic message instead of the interpreter's nice
22/// diagnostic, but our ability to detect UB is unchanged.
23/// But if `check_language_ub` is used when the check is actually for library UB, the check is
24/// omitted in const-eval/Miri and thus UB might occur undetected. Even if we eventually execute
25/// language UB which relies on the library UB, the backtrace Miri reports may be far removed from
26/// original cause.
27///
28/// These checks are behind a condition which is evaluated at codegen time, not expansion time like
29/// [`debug_assert`]. This means that a standard library built with optimizations and debug
30/// assertions disabled will have these checks optimized out of its monomorphizations, but if a
31/// caller of the standard library has debug assertions enabled and monomorphizes an expansion of
32/// this macro, that monomorphization will contain the check.
33///
34/// Since these checks cannot be optimized out in MIR, some care must be taken in both call and
35/// implementation to mitigate their compile-time overhead. Calls to this macro always expand to
36/// this structure:
37/// ```ignore (pseudocode)
38/// if ::core::intrinsics::check_language_ub() {
39///     precondition_check(args)
40/// }
41/// ```
42/// where `precondition_check` is monomorphic with the attributes `#[rustc_nounwind]`, `#[inline]` and
43/// `#[rustc_no_mir_inline]`. This combination of attributes ensures that the actual check logic is
44/// compiled only once and generates a minimal amount of IR because the check cannot be inlined in
45/// MIR, but *can* be inlined and fully optimized by a codegen backend.
46///
47/// Callers should avoid introducing any other `let` bindings or any code outside this macro in
48/// order to call it. Since the precompiled standard library is built with full debuginfo and these
49/// variables cannot be optimized out in MIR, an innocent-looking `let` can produce enough
50/// debuginfo to have a measurable compile-time impact on debug builds.
51#[macro_export]
52#[unstable(feature = "ub_checks", issue = "none")]
53#[allow_internal_unstable(coverage_attribute)]
54macro_rules! assert_unsafe_precondition {
55    ($kind:ident, $message:expr, ($($name:ident:$ty:ty = $arg:expr),*$(,)?) => $e:expr $(,)?) => {
56        {
57            // This check is inlineable, but not by the MIR inliner.
58            // The reason for this is that the MIR inliner is in an exceptionally bad position
59            // to think about whether or not to inline this. In MIR, this call is gated behind `debug_assertions`,
60            // which will codegen to `false` in release builds. Inlining the check would be wasted work in that case and
61            // would be bad for compile times.
62            //
63            // LLVM on the other hand sees the constant branch, so if it's `false`, it can immediately delete it without
64            // inlining the check. If it's `true`, it can inline it and get significantly better performance.
65            #[rustc_no_mir_inline]
66            #[inline]
67            #[rustc_nounwind]
68            #[track_caller]
69            #[ferrocene::annotation(
70                "This code cannot be covered because it causes an non-unwinding panic, which means it cannot be caught by any means in a test."
71            )]
72            const fn precondition_check($($name:$ty),*) {
73                if !$e {
74                    let msg = concat!("unsafe precondition(s) violated: ", $message,
75                        "\n\nThis indicates a bug in the program. \
76                        This Undefined Behavior check is optional, and cannot be relied on for safety.");
77                    // blocked on fmt::Arguments
78                    #[cfg(not(feature = "ferrocene_certified"))]
79                    ::core::panicking::panic_nounwind_fmt(::core::fmt::Arguments::new_const(&[msg]), false);
80                    #[cfg(feature = "ferrocene_certified")]
81                    ::core::panicking::panic_nounwind(msg);
82                }
83            }
84
85            if ::core::ub_checks::$kind() {
86                precondition_check($($arg,)*);
87            }
88        }
89    };
90}
91#[unstable(feature = "ub_checks", issue = "none")]
92pub use assert_unsafe_precondition;
93/// Checking library UB is always enabled when UB-checking is done
94/// (and we use a reexport so that there is no unnecessary wrapper function).
95#[unstable(feature = "ub_checks", issue = "none")]
96pub use intrinsics::ub_checks as check_library_ub;
97
98/// Determines whether we should check for language UB.
99///
100/// The intention is to not do that when running in the interpreter, as that one has its own
101/// language UB checks which generally produce better errors.
102#[inline]
103#[rustc_allow_const_fn_unstable(const_eval_select)]
104pub(crate) const fn check_language_ub() -> bool {
105    // Only used for UB checks so we may const_eval_select.
106    intrinsics::ub_checks()
107        && const_eval_select!(
108            @capture { } -> bool:
109            if const {
110                // Always disable UB checks.
111                false
112            } else {
113                // Disable UB checks in Miri.
114                !cfg!(miri)
115            }
116        )
117}
118
119/// Checks whether `ptr` is properly aligned with respect to the given alignment, and
120/// if `is_zst == false`, that `ptr` is not null.
121///
122/// In `const` this is approximate and can fail spuriously. It is primarily intended
123/// for `assert_unsafe_precondition!` with `check_language_ub`, in which case the
124/// check is anyway not executed in `const`.
125#[inline]
126#[rustc_allow_const_fn_unstable(const_eval_select)]
127#[cfg(any(
128    not(feature = "ferrocene_certified"),
129    all(feature = "ferrocene_certified", debug_assertions)
130))]
131pub(crate) const fn maybe_is_aligned_and_not_null(
132    ptr: *const (),
133    align: usize,
134    is_zst: bool,
135) -> bool {
136    // This is just for safety checks so we can const_eval_select.
137    maybe_is_aligned(ptr, align) && (is_zst || !ptr.is_null())
138}
139
140/// Checks whether `ptr` is properly aligned with respect to the given alignment.
141///
142/// In `const` this is approximate and can fail spuriously. It is primarily intended
143/// for `assert_unsafe_precondition!` with `check_language_ub`, in which case the
144/// check is anyway not executed in `const`.
145#[inline]
146#[rustc_allow_const_fn_unstable(const_eval_select)]
147pub(crate) const fn maybe_is_aligned(ptr: *const (), align: usize) -> bool {
148    // This is just for safety checks so we can const_eval_select.
149    const_eval_select!(
150        @capture { ptr: *const (), align: usize } -> bool:
151        if const {
152            true
153        } else {
154            ptr.is_aligned_to(align)
155        }
156    )
157}
158
159#[inline]
160pub(crate) const fn is_valid_allocation_size(size: usize, len: usize) -> bool {
161    let max_len = if size == 0 { usize::MAX } else { isize::MAX as usize / size };
162    len <= max_len
163}
164
165/// Checks whether the regions of memory starting at `src` and `dst` of size
166/// `count * size` do *not* overlap.
167///
168/// Note that in const-eval this function just returns `true` and therefore must
169/// only be used with `assert_unsafe_precondition!`, similar to `is_aligned_and_not_null`.
170#[inline]
171#[rustc_allow_const_fn_unstable(const_eval_select)]
172pub(crate) const fn maybe_is_nonoverlapping(
173    src: *const (),
174    dst: *const (),
175    size: usize,
176    count: usize,
177) -> bool {
178    // This is just for safety checks so we can const_eval_select.
179    const_eval_select!(
180        @capture { src: *const (), dst: *const (), size: usize, count: usize } -> bool:
181        if const {
182            true
183        } else {
184            let src_usize = src.addr();
185            let dst_usize = dst.addr();
186            let Some(size) = size.checked_mul(count) else {
187                crate::panicking::panic_nounwind(
188                    "is_nonoverlapping: `size_of::<T>() * count` overflows a usize",
189                )
190            };
191            let diff = src_usize.abs_diff(dst_usize);
192            // If the absolute distance between the ptrs is at least as big as the size of the buffer,
193            // they do not overlap.
194            diff >= size
195        }
196    )
197}