All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miguel Ojeda <ojeda@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jarkko Sakkinen <jarkko@kernel.org>,
	Miguel Ojeda <ojeda@kernel.org>, Gary Guo <gary@garyguo.net>,
	Alex Gaynor <alex.gaynor@gmail.com>,
	Wedson Almeida Filho <wedsonaf@google.com>
Subject: [PATCH v8 13/31] rust: add `build_error` crate
Date: Tue,  2 Aug 2022 03:50:00 +0200	[thread overview]
Message-ID: <20220802015052.10452-14-ojeda@kernel.org> (raw)
In-Reply-To: <20220802015052.10452-1-ojeda@kernel.org>

From: Gary Guo <gary@garyguo.net>

The `build_error` crate provides the `build_error` function which
is then used to provide the `build_error!` and the `build_assert!`
macros.

`build_assert!` is intended to be used when `static_assert!` cannot
be used, e.g. when the condition refers to generic parameters or
parameters of an inline function.

Co-developed-by: Alex Gaynor <alex.gaynor@gmail.com>
Signed-off-by: Alex Gaynor <alex.gaynor@gmail.com>
Co-developed-by: Wedson Almeida Filho <wedsonaf@google.com>
Signed-off-by: Wedson Almeida Filho <wedsonaf@google.com>
Signed-off-by: Gary Guo <gary@garyguo.net>
Co-developed-by: Miguel Ojeda <ojeda@kernel.org>
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
---
 rust/build_error.rs | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 rust/build_error.rs

diff --git a/rust/build_error.rs b/rust/build_error.rs
new file mode 100644
index 000000000000..bbd3a05440b2
--- /dev/null
+++ b/rust/build_error.rs
@@ -0,0 +1,29 @@
+// SPDX-License-Identifier: GPL-2.0
+
+//! Build-time error.
+//!
+//! This crate provides a function `build_error`, which will panic in
+//! compile-time if executed in const context, and will cause a build error
+//! if not executed at compile time and the optimizer does not optimise away the
+//! call.
+//!
+//! It is used by `build_assert!` in the kernel crate, allowing checking of
+//! conditions that could be checked statically, but could not be enforced in
+//! Rust yet (e.g. perform some checks in const functions, but those
+//! functions could still be called in the runtime).
+
+#![no_std]
+
+/// Panics if executed in const context, or triggers a build error if not.
+#[inline(never)]
+#[cold]
+#[export_name = "rust_build_error"]
+#[track_caller]
+pub const fn build_error(msg: &'static str) -> ! {
+    panic!("{}", msg);
+}
+
+#[cfg(CONFIG_RUST_BUILD_ASSERT_WARN)]
+#[link_section = ".gnu.warning.rust_build_error"]
+#[used]
+static BUILD_ERROR_WARNING: [u8; 45] = *b"call to build_error present after compilation";
-- 
2.37.1


  parent reply	other threads:[~2022-08-02  1:53 UTC|newest]

Thread overview: 129+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02  1:49 [PATCH v8 00/31] Rust support Miguel Ojeda
2022-08-02  1:49 ` Miguel Ojeda
2022-08-02  1:49 ` Miguel Ojeda
2022-08-02  1:49 ` Miguel Ojeda
2022-08-02  1:49 ` [PATCH v8 01/31] kallsyms: use `sizeof` instead of hardcoded size Miguel Ojeda
2022-08-02  1:49 ` [PATCH v8 02/31] kallsyms: avoid hardcoding buffer size Miguel Ojeda
2022-08-02  8:29   ` David Laight
2022-08-02  9:45     ` Rasmus Villemoes
2022-08-02  1:49 ` [PATCH v8 03/31] kallsyms: add static relationship between `KSYM_NAME_LEN{,_BUFFER}` Miguel Ojeda
2022-08-02  1:49 ` [PATCH v8 04/31] kallsyms: support "big" kernel symbols Miguel Ojeda
2022-08-02  1:49 ` [PATCH v8 05/31] kallsyms: increase maximum kernel symbol length to 512 Miguel Ojeda
2022-08-02  1:49 ` [PATCH v8 06/31] workqueue: introduce `__INIT_WORK_WITH_KEY` Miguel Ojeda
2022-08-15 21:14   ` Tejun Heo
2022-08-15 21:53     ` Miguel Ojeda
2022-08-02  1:49 ` [PATCH v8 07/31] locking/spinlock: introduce `__spin_lock_init` Miguel Ojeda
2022-08-03 20:58   ` Boqun Feng
2022-08-02  1:49 ` [PATCH v8 08/31] locking/spinlock: introduce `_raw_spin_lock_init` Miguel Ojeda
2022-08-03 21:00   ` Boqun Feng
2022-08-02  1:49 ` [PATCH v8 09/31] rust: add C helpers Miguel Ojeda
2022-08-02  1:49 ` [PATCH v8 10/31] rust: add `compiler_builtins` crate Miguel Ojeda
2022-08-02  1:49 ` [PATCH v8 11/31] rust: import upstream `alloc` crate Miguel Ojeda
2022-08-02  1:49 ` [PATCH v8 12/31] rust: adapt `alloc` crate to the kernel Miguel Ojeda
2022-08-02  1:50 ` Miguel Ojeda [this message]
2022-08-02  1:50 ` [PATCH v8 14/31] rust: add `macros` crate Miguel Ojeda
2022-08-02  1:50 ` [PATCH v8 15/31] rust: add `bindings` crate Miguel Ojeda
2022-08-02  1:50 ` [PATCH v8 16/31] rust: add `kernel` crate's `sync` module Miguel Ojeda
2022-08-02  1:50 ` [PATCH v8 17/31] rust: add `kernel` crate Miguel Ojeda
2022-08-02 13:34   ` Greg Kroah-Hartman
2022-08-02 14:33     ` Miguel Ojeda
2022-08-02 14:36       ` Greg Kroah-Hartman
2022-08-02 14:53         ` Miguel Ojeda
2022-08-03  7:30           ` Greg Kroah-Hartman
2022-08-02  1:50 ` [PATCH v8 18/31] rust: export generated symbols Miguel Ojeda
2022-08-02  1:50 ` [PATCH v8 19/31] vsprintf: add new `%pA` format specifier Miguel Ojeda
2022-08-02  1:50 ` [PATCH v8 20/31] scripts: checkpatch: diagnose uses of `%pA` in the C side as errors Miguel Ojeda
2022-08-02  1:50 ` [PATCH v8 21/31] scripts: checkpatch: enable language-independent checks for Rust Miguel Ojeda
2022-08-02  1:50 ` [PATCH v8 22/31] scripts: add `rustdoc_test_{builder,gen}.py` scripts Miguel Ojeda
2022-08-02  1:50 ` [PATCH v8 23/31] scripts: add `generate_rust_analyzer.py` scripts Miguel Ojeda
2022-08-02  1:50 ` [PATCH v8 24/31] scripts: decode_stacktrace: demangle Rust symbols Miguel Ojeda
2022-08-02  1:50 ` [PATCH v8 25/31] configs: add `rust` config Miguel Ojeda
2022-08-02  1:50 ` [PATCH v8 26/31] docs: add Rust documentation Miguel Ojeda
2022-08-02  1:50 ` [PATCH v8 27/31] Kbuild: add Rust support Miguel Ojeda
2022-08-02  1:50   ` Miguel Ojeda
2022-08-02  1:50   ` Miguel Ojeda
2022-08-02  1:50   ` Miguel Ojeda
2022-08-02  1:50   ` Miguel Ojeda
2022-08-17 14:39   ` Arnd Bergmann
2022-08-17 14:39     ` Arnd Bergmann
2022-08-17 14:39     ` Arnd Bergmann
2022-08-17 14:39     ` Arnd Bergmann
2022-08-17 14:39     ` Arnd Bergmann
2022-08-17 15:13     ` Miguel Ojeda
2022-08-17 15:13       ` Miguel Ojeda
2022-08-17 15:13       ` Miguel Ojeda
2022-08-17 15:13       ` Miguel Ojeda
2022-08-17 15:24       ` Arnd Bergmann
2022-08-17 15:24         ` Arnd Bergmann
2022-08-17 15:24         ` Arnd Bergmann
2022-08-17 23:13         ` Miguel Ojeda
2022-08-17 23:13           ` Miguel Ojeda
2022-08-17 23:13           ` Miguel Ojeda
2022-08-17 23:13           ` Miguel Ojeda
2022-08-17 16:11       ` Björn Roy Baron
2022-08-17 16:11         ` Björn Roy Baron
2022-08-17 16:11         ` Björn Roy Baron
2022-08-17 16:11         ` Björn Roy Baron
2022-08-17 22:42         ` Miguel Ojeda
2022-08-17 22:42           ` Miguel Ojeda
2022-08-17 22:42           ` Miguel Ojeda
2022-08-17 22:42           ` Miguel Ojeda
2022-09-06 18:08   ` Masahiro Yamada
2022-09-06 18:08     ` Masahiro Yamada
2022-09-06 18:08     ` Masahiro Yamada
2022-09-06 18:08     ` Masahiro Yamada
2022-09-06 18:08     ` Masahiro Yamada
2022-09-06 23:34     ` Michael Ellerman
2022-09-06 23:34       ` Michael Ellerman
2022-09-06 23:34       ` Michael Ellerman
2022-09-06 23:34       ` Michael Ellerman
2022-09-06 23:34       ` Michael Ellerman
2022-08-02  1:50 ` [PATCH v8 28/31] samples: add Rust examples Miguel Ojeda
2022-08-02 14:07   ` Konstantin Shelekhin
2022-08-02 20:04     ` Wei Liu
2022-08-03  9:23       ` Konstantin Shelekhin
2022-08-04 20:31     ` Miguel Ojeda
2022-08-05 11:40       ` Konstantin Shelekhin
2022-08-06 11:58         ` Miguel Ojeda
2022-08-02  1:50 ` [PATCH v8 29/31] MAINTAINERS: Rust Miguel Ojeda
2022-08-02  2:25   ` Boqun Feng
2022-08-02  3:41     ` Miguel Ojeda
2022-08-02 14:53     ` Gary Guo
2022-08-04 10:15     ` bjorn3
2022-08-02  1:50 ` [PATCH v8 30/31] [RFC] drivers: gpio: PrimeCell PL061 in Rust Miguel Ojeda
2022-08-02  1:50 ` [PATCH v8 31/31] [RFC] drivers: android: Binder IPC " Miguel Ojeda
2022-08-02 12:26 ` [PATCH v8 00/31] Rust support Matthew Wilcox
2022-08-02 12:26   ` Matthew Wilcox
2022-08-02 12:26   ` Matthew Wilcox
2022-08-02 12:26   ` Matthew Wilcox
2022-08-02 12:26   ` Matthew Wilcox
2022-08-02 13:45   ` Miguel Ojeda
2022-08-02 13:45     ` Miguel Ojeda
2022-08-02 13:45     ` Miguel Ojeda
2022-08-02 13:45     ` Miguel Ojeda
2022-08-02 13:45     ` Miguel Ojeda
2022-08-02 13:48     ` Christoph Hellwig
2022-08-02 13:48       ` Christoph Hellwig
2022-08-02 13:48       ` Christoph Hellwig
2022-08-02 13:48       ` Christoph Hellwig
2022-08-02 13:48       ` Christoph Hellwig
2022-08-02 14:16       ` Miguel Ojeda
2022-08-02 14:16         ` Miguel Ojeda
2022-08-02 14:16         ` Miguel Ojeda
2022-08-02 14:16         ` Miguel Ojeda
2022-08-02 14:16         ` Miguel Ojeda
2022-08-02 14:01     ` Matthew Wilcox
2022-08-02 14:01       ` Matthew Wilcox
2022-08-02 14:01       ` Matthew Wilcox
2022-08-02 14:01       ` Matthew Wilcox
2022-08-02 14:01       ` Matthew Wilcox
2022-08-02 15:09       ` Miguel Ojeda
2022-08-02 15:09         ` Miguel Ojeda
2022-08-02 15:09         ` Miguel Ojeda
2022-08-02 15:09         ` Miguel Ojeda
2022-08-02 15:09         ` Miguel Ojeda
2022-08-02 17:46         ` Miguel Ojeda
2022-08-02 17:46           ` Miguel Ojeda
2022-08-02 17:46           ` Miguel Ojeda
2022-08-02 17:46           ` Miguel Ojeda
2022-08-02 17:46           ` Miguel Ojeda

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220802015052.10452-14-ojeda@kernel.org \
    --to=ojeda@kernel.org \
    --cc=alex.gaynor@gmail.com \
    --cc=gary@garyguo.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jarkko@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=wedsonaf@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.