From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
Subject: [PULL 11/30] docs: rust: update for newer minimum supported version
Date: Tue, 6 May 2025 17:29:06 +0200 [thread overview]
Message-ID: <20250506152927.222671-12-pbonzini@redhat.com> (raw)
In-Reply-To: <20250506152927.222671-1-pbonzini@redhat.com>
Remove leftover notes for Rust changes between 1.63.0 and 1.77.0.
Reviewed-by: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
docs/devel/rust.rst | 15 +--------------
1 file changed, 1 insertion(+), 14 deletions(-)
diff --git a/docs/devel/rust.rst b/docs/devel/rust.rst
index 557cee72f39..4de86375021 100644
--- a/docs/devel/rust.rst
+++ b/docs/devel/rust.rst
@@ -71,16 +71,9 @@ Building Rust code with ``--enable-modules`` is not supported yet.
Supported tools
'''''''''''''''
-QEMU supports rustc version 1.63.0 and newer. Notably, the following features
+QEMU supports rustc version 1.77.0 and newer. Notably, the following features
are missing:
-* Generic Associated Types (1.65.0)
-
-* ``CStr::from_bytes_with_nul()`` as a ``const`` function (1.72.0).
-
-* "Return position ``impl Trait`` in Traits" (1.75.0, blocker for including
- the pinned-init create).
-
* inline const expression (stable in 1.79.0), currently worked around with
associated constants in the ``FnCall`` trait.
@@ -105,12 +98,6 @@ are missing:
__ https://github.com/rust-lang/rust/pull/125258
-It is expected that QEMU will advance its minimum supported version of
-rustc to 1.77.0 as soon as possible; as of January 2025, blockers
-for that right now are Debian bookworm and 32-bit MIPS processors.
-This unfortunately means that references to statics in constants will
-remain an issue.
-
QEMU also supports version 0.60.x of bindgen, which is missing option
``--generate-cstr``. This option requires version 0.66.x and will
be adopted as soon as supporting these older versions is not necessary
--
2.49.0
next prev parent reply other threads:[~2025-05-06 15:32 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 15:28 [PULL 00/30] Rust, wasm changes for 2025-05-06 Paolo Bonzini
2025-05-06 15:28 ` [PULL 01/30] lcitool: use newer Rust for Debian and Ubuntu Paolo Bonzini
2025-09-03 13:54 ` Marc-André Lureau
2025-09-03 13:59 ` Paolo Bonzini
2025-09-04 19:38 ` Marc-André Lureau
2025-09-05 5:16 ` Paolo Bonzini
2025-09-05 5:17 ` Paolo Bonzini
2025-09-05 12:06 ` Alex Bennée
2025-05-06 15:28 ` [PULL 02/30] meson, cargo: require Rust 1.77.0 Paolo Bonzini
2025-05-06 15:28 ` [PULL 03/30] rust: use std::ffi instead of std::os::raw Paolo Bonzini
2025-05-06 15:28 ` [PULL 04/30] rust: let bilge use "let ... else" Paolo Bonzini
2025-05-06 15:29 ` [PULL 05/30] rust: qemu_api_macros: make pattern matching more readable and efficient Paolo Bonzini
2025-05-06 15:29 ` [PULL 06/30] rust: use MaybeUninit::zeroed() in const context Paolo Bonzini
2025-05-06 15:29 ` [PULL 07/30] rust: qom: fix TODO about zeroability of classes Paolo Bonzini
2025-05-06 15:29 ` [PULL 08/30] rust: enable clippy::ptr_cast_constness Paolo Bonzini
2025-05-06 15:29 ` [PULL 09/30] rust: remove offset_of replacement Paolo Bonzini
2025-05-06 15:29 ` [PULL 10/30] rust: replace c_str! with c"" literals Paolo Bonzini
2025-05-06 15:29 ` Paolo Bonzini [this message]
2025-05-06 15:29 ` [PULL 12/30] target/i386/emulate: fix target_ulong format strings Paolo Bonzini
2025-05-06 15:29 ` [PULL 13/30] rust: clippy: enable uninlined_format_args lint Paolo Bonzini
2025-05-06 15:29 ` [PULL 14/30] ci: run RISC-V cross jobs by default Paolo Bonzini
2025-05-06 15:29 ` [PULL 15/30] docs: build-system: fix typo Paolo Bonzini
2025-05-06 15:29 ` [PULL 16/30] target/arm/helper.c: Fix type conflict of GLib function pointers Paolo Bonzini
2025-05-06 15:29 ` [PULL 17/30] target/i386/cpu.c: " Paolo Bonzini
2025-05-06 15:29 ` [PULL 18/30] target/ppc: " Paolo Bonzini
2025-05-06 15:29 ` [PULL 19/30] target/s390x: " Paolo Bonzini
2025-05-06 15:29 ` [PULL 20/30] include/glib-compat.h: Poison g_list_sort and g_slist_sort Paolo Bonzini
2025-05-06 15:29 ` [PULL 21/30] util/cacheflush.c: Update cache flushing mechanism for Emscripten Paolo Bonzini
2025-05-06 15:29 ` [PULL 22/30] block: Add including of ioctl header for Emscripten build Paolo Bonzini
2025-05-06 15:29 ` [PULL 23/30] block: Fix type conflict of the copy_file_range stub Paolo Bonzini
2025-05-06 15:29 ` [PULL 24/30] include/qemu/osdep.h: Add Emscripten-specific OS dependencies Paolo Bonzini
2025-05-06 15:29 ` [PULL 25/30] Disable options unsupported on Emscripten Paolo Bonzini
2025-05-06 15:29 ` [PULL 26/30] util: exclude mmap-alloc.c from compilation target " Paolo Bonzini
2025-05-06 15:29 ` [PULL 27/30] util: Add coroutine backend for emscripten Paolo Bonzini
2025-05-06 15:29 ` [PULL 28/30] meson: Add wasm build in build scripts Paolo Bonzini
2025-05-06 15:29 ` [PULL 29/30] tests: Add Dockerfile containing dependencies for Emscripten build Paolo Bonzini
2025-05-06 15:29 ` [PULL 30/30] gitlab: Enable CI for wasm build Paolo Bonzini
2025-05-08 14:26 ` [PULL 00/30] Rust, wasm changes for 2025-05-06 Stefan Hajnoczi
2025-05-08 16:08 ` Paolo Bonzini
2025-05-08 16:53 ` Stefan Hajnoczi
2025-05-08 17:05 ` Thomas Huth
2025-05-08 17:15 ` Paolo Bonzini
2025-05-09 14:11 ` Stefan Hajnoczi
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=20250506152927.222671-12-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).