public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux•org.uk>
To: Christian Schrefl <chrisi.schrefl@gmail•com>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail•com>,
	Alice Ryhl <aliceryhl@google•com>,
	Ard Biesheuvel <ardb@kernel•org>,
	Jamie Cunliffe <Jamie.Cunliffe@arm•com>,
	Will Deacon <will@kernel•org>,
	Catalin Marinas <catalin.marinas@arm•com>,
	Miguel Ojeda <ojeda@kernel•org>,
	a.hindborg@kernel•org, acourbot@nvidia•com,
	akpm@linux-foundation•org, anton.ivanov@cambridgegreys•com,
	bjorn3_gh@protonmail•com, boqun.feng@gmail•com, dakr@kernel•org,
	david@davidgow•net, gary@garyguo•net, johannes@sipsolutions•net,
	justinstitt@google•com, linux-arm-kernel@lists•infradead.org,
	linux-kbuild@vger•kernel.org, linux-kernel@vger•kernel.org,
	linux-mm@kvack•org, linux-um@lists•infradead.org,
	llvm@lists•linux.dev, lossin@kernel•org, mark.rutland@arm•com,
	mmaurer@google•com, morbo@google•com, nathan@kernel•org,
	nick.desaulniers+lkml@gmail•com, nicolas.schier@linux•dev,
	nsc@kernel•org, peterz@infradead•org, richard@nod•at,
	rust-for-linux@vger•kernel.org, tmgross@umich•edu,
	urezki@gmail•com
Subject: Re: [PATCH v2 0/3] Inline helpers into Rust without full LTO
Date: Thu, 26 Mar 2026 15:18:07 +0000	[thread overview]
Message-ID: <acVOL5Psz6kHlhq2@shell.armlinux.org.uk> (raw)
In-Reply-To: <9cf5a94c-0f37-446c-b63d-ddac5674d220@gmail.com>

On Thu, Mar 26, 2026 at 03:31:26PM +0100, Christian Schrefl wrote:
> Hi Miguel,
> 
> On 3/26/26 2:47 PM, Miguel Ojeda wrote:
> > On Thu, Mar 26, 2026 at 11:10 AM Alice Ryhl <aliceryhl@google•com> wrote:
> >>
> >> I noticed that the Makefile currently uses the arm-unknown-linux-gnueabi
> >> target. It should probably not be -linux target to avoid this? Probably
> >> it should just be armv7a-none-eabi, right? We gate HAVE_RUST on
> >> CPU_32v7, so we should not need to consider the other variants.
> > 
> > I think Christian tried several targets back then and eventually
> > picked that one.
> > 
> > Christian: what was the reason to pick the `-linux-` one? e.g. was
> > there something you wanted to rely on that target spec that you
> > couldn't enable or disable via `rustc` flags or similar?
> 
> It should probably be fine to use armv7a-none-eabi. I've mostly used
> arm-unknown-linux-gnueabi

I'm not sure if this is still true, but I believe it used to be the case
that the -linux-gnueabi target has one behaviour for enums (fixed size)
whereas -none-eabi, the size of the type depends on the range of values
included in the enum.

Certianly, when Arm Ltd were proposing EABI, EABI had the latter
behaviour, and I think there were cases where Linux used "enum" in
its UAPI.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!


  reply	other threads:[~2026-03-26 15:18 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260203-inline-helpers-v2-0-beb8547a03c9@google.com>
2026-03-22 19:21 ` [PATCH v2 0/3] Inline helpers into Rust without full LTO Miguel Ojeda
2026-03-22 19:38   ` Miguel Ojeda
2026-03-23 13:54     ` Mark Brown
2026-03-23 14:53       ` Miguel Ojeda
2026-03-22 19:46   ` Miguel Ojeda
2026-03-23  8:49     ` Marek Szyprowski
2026-03-25  1:58       ` Miguel Ojeda
2026-03-26 21:12     ` Arnd Bergmann
2026-03-27  8:02       ` Miguel Ojeda
2026-03-27  8:16       ` Marek Szyprowski
2026-03-23  0:03   ` Miguel Ojeda
2026-03-23  3:04     ` Andrew Lunn
2026-03-23  3:24       ` Miguel Ojeda
2026-03-23 12:54         ` Andrew Lunn
2026-03-23 13:13           ` Gary Guo
2026-03-23 13:28             ` Andrew Lunn
2026-03-23 13:34               ` Miguel Ojeda
2026-03-23 14:39               ` Alice Ryhl
2026-03-23 13:14           ` Miguel Ojeda
2026-03-23 10:03     ` Russell King (Oracle)
2026-03-23 13:26       ` Miguel Ojeda
2026-03-26 10:10       ` Alice Ryhl
2026-03-26 13:47         ` Miguel Ojeda
2026-03-26 14:31           ` Christian Schrefl
2026-03-26 15:18             ` Russell King (Oracle) [this message]
2026-03-26 17:30               ` Miguel Ojeda
2026-03-30 21:09                 ` Christian Schrefl
2026-03-31 11:44                   ` Arnd Bergmann
2026-03-26 21:33               ` Arnd Bergmann
2026-03-27  7:56                 ` Geert Uytterhoeven
2026-03-27  9:02                   ` Arnd Bergmann
2026-03-27 13:41                     ` Arnd Bergmann
2026-03-30 12:03                     ` Geert Uytterhoeven
2026-03-30 12:13                       ` Arnd Bergmann
2026-03-30 12:17                         ` Geert Uytterhoeven
2026-03-26 17:31             ` Miguel Ojeda
2026-03-26  2:42   ` Nathan Chancellor
2026-03-26 17:13     ` Miguel Ojeda
2026-03-26  5:34   ` David Gow

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=acVOL5Psz6kHlhq2@shell.armlinux.org.uk \
    --to=linux@armlinux$(echo .)org.uk \
    --cc=Jamie.Cunliffe@arm$(echo .)com \
    --cc=a.hindborg@kernel$(echo .)org \
    --cc=acourbot@nvidia$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=aliceryhl@google$(echo .)com \
    --cc=anton.ivanov@cambridgegreys$(echo .)com \
    --cc=ardb@kernel$(echo .)org \
    --cc=bjorn3_gh@protonmail$(echo .)com \
    --cc=boqun.feng@gmail$(echo .)com \
    --cc=catalin.marinas@arm$(echo .)com \
    --cc=chrisi.schrefl@gmail$(echo .)com \
    --cc=dakr@kernel$(echo .)org \
    --cc=david@davidgow$(echo .)net \
    --cc=gary@garyguo$(echo .)net \
    --cc=johannes@sipsolutions$(echo .)net \
    --cc=justinstitt@google$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kbuild@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-mm@kvack$(echo .)org \
    --cc=linux-um@lists$(echo .)infradead.org \
    --cc=llvm@lists$(echo .)linux.dev \
    --cc=lossin@kernel$(echo .)org \
    --cc=mark.rutland@arm$(echo .)com \
    --cc=miguel.ojeda.sandonis@gmail$(echo .)com \
    --cc=mmaurer@google$(echo .)com \
    --cc=morbo@google$(echo .)com \
    --cc=nathan@kernel$(echo .)org \
    --cc=nick.desaulniers+lkml@gmail$(echo .)com \
    --cc=nicolas.schier@linux$(echo .)dev \
    --cc=nsc@kernel$(echo .)org \
    --cc=ojeda@kernel$(echo .)org \
    --cc=peterz@infradead$(echo .)org \
    --cc=richard@nod$(echo .)at \
    --cc=rust-for-linux@vger$(echo .)kernel.org \
    --cc=tmgross@umich$(echo .)edu \
    --cc=urezki@gmail$(echo .)com \
    --cc=will@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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