All of lore.kernel.org
 help / color / mirror / Atom feed
From: Younes Akhouayri <git@younes.io>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Alexandre Courbot" <acourbot@nvidia.com>,
	"Yury Norov" <yury.norov@gmail.com>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Daniel Almeida" <daniel.almeida@collabora.com>,
	"Tamir Duberstein" <tamird@kernel.org>,
	"Onur Özkan" <work@onurozkan.dev>,
	"Rust For Linux" <rust-for-linux@vger.kernel.org>,
	Stable <stable@vger.kernel.org>,
	"Younes Akhouayri" <git@younes.io>
Subject: Re: [PATCH] rust: num: reject bool conversion to signed one-bit Bounded
Date: Sat, 15 Aug 2026 16:56:05 +0200 (CEST)	[thread overview]
Message-ID: <P-4v-PO--F-9@younes.io> (raw)
In-Reply-To: <CANiq72kAkDeyqPKHHMT3gRNyC35R+934jNNQOKKytMpmwPwLCg@mail.gmail.com>

I tested this in a Linux Docker container with Rust 1.85.0 and two CPUs,
alternating 50 builds of `rust/kernel.o` for the parent and v1.

The difference was 1.16 ms (0.066%), similar to the identical-source
control at 0.96 ms. So I could not measure a clear slowdown from the
patch.

Thanks,
Younes

  reply	other threads:[~2026-08-15 14:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-15  8:06 [PATCH] rust: num: reject bool conversion to signed one-bit Bounded Younes Akhouayri via B4 Relay
2026-08-15  8:06 ` Younes Akhouayri
2026-08-15  9:47 ` Miguel Ojeda
2026-08-15 14:56   ` Younes Akhouayri [this message]
2026-08-15 15:00     ` Miguel Ojeda
2026-08-15 18:50 ` Gary Guo

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=P-4v-PO--F-9@younes.io \
    --to=git@younes.io \
    --cc=a.hindborg@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=gary@garyguo.net \
    --cc=lossin@kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tamird@kernel.org \
    --cc=tmgross@umich.edu \
    --cc=work@onurozkan.dev \
    --cc=yury.norov@gmail.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.