[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aYnMKFmB3Ve5-2OS@alpha.franken.de>
Date: Mon, 9 Feb 2026 12:59:36 +0100
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Thomas Weißschuh <thomas.weissschuh@...utronix.de>
Cc: "Maciej W. Rozycki" <macro@...am.me.uk>, linux-mips@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] MIPS: Implement ARCH_HAS_CC_CAN_LINK
On Fri, Jan 09, 2026 at 11:08:49AM +0100, Thomas Weißschuh wrote:
> The generic CC_CAN_LINK detection does not handle different byte orders
> or ABIs. This may lead to userprogs which are not actually runnable on
> the target kernel.
>
> Use architecture-specific logic supporting byte orders instead.
>
> Modern 64-bit toolchains default to a n32 libc, which are not
> supported by all kernel configurations, as MIPS32_N32 is optional.
> On 64-bit, test for a n32 ABI libc first and fall back to o64 and
> o32 if necessary.
>
> Link: https://lore.kernel.org/lkml/20260105100507-14db55e3-aa71-48bf-a6ac-33b186bd082f@linutronix.de/
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@...utronix.de>
> ---
> Changes in v2:
> - Use -mabi= over -m32/-m64
> - Link to v1: https://lore.kernel.org/r/20251222-cc-can-link-mips-v1-1-6d87a8afe442@linutronix.de
> ---
> arch/mips/Kconfig | 28 ++++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
applied to mips-next
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists