[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250227163319.5b19a68a@gandalf.local.home>
Date: Thu, 27 Feb 2025 16:33:19 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: David Laight <david.laight.linux@...il.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Martin Uecker
<uecker@...raz.at>, Ralf Jung <post@...fj.de>, "Paul E. McKenney"
<paulmck@...nel.org>, Alice Ryhl <aliceryhl@...gle.com>, Ventura Jack
<venturajack85@...il.com>, Kent Overstreet <kent.overstreet@...ux.dev>,
Gary Guo <gary@...yguo.net>, airlied@...il.com, boqun.feng@...il.com,
ej@...i.de, gregkh@...uxfoundation.org, hch@...radead.org, hpa@...or.com,
ksummit@...ts.linux.dev, linux-kernel@...r.kernel.org,
miguel.ojeda.sandonis@...il.com, rust-for-linux@...r.kernel.org
Subject: Re: C aggregate passing (Rust kernel policy)
On Thu, 27 Feb 2025 20:47:22 +0000
David Laight <david.laight.linux@...il.com> wrote:
> Except that (IIRC) it is actually valid for the compiler to write something
> entirely unrelated to a memory location before writing the expected value.
> (eg use it instead of stack for a register spill+reload.)
> Not gcc doesn't do that - but the standard lets it do it.
I call that a bug in the specification ;-)
-- Steve
Powered by blists - more mailing lists