Re: [Buildroot] [PATCH v3 02/11] arch: Introduce LoongArch64

From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: buildroot@buildroot.org,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Romain Naour <romain.naour@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Dick Olsson <hi@senzilla.io>
Subject: Re: [Buildroot] [PATCH v3 02/11] arch: Introduce LoongArch64
Date: Sat, 05 Jul 2025 14:17:15 +0200	[thread overview]
Message-ID: <3f1060fd8783b35211b3de718d350dd1@free.fr> (raw)
In-Reply-To: <20250618-loongarch-v3-2-d11baae32eea@flygoat.com>

Hi Jiaxun,

On 18/06/2025 20:20, Jiaxun Yang wrote:
> Introduce LoongArch64 at architecture level.
> 
> Config.in.loongarch is prepared for possible loongarch32
> enablement in future, thus BR2_ARCH_IS_64 is being depended
> by some 64bit only options.
> 
> Internal toolchain is supported, as our minimal binutils
> version is already beyond LoongArch minimal version and
> GCC option is limited by BR2_ARCH_NEEDS_GCC_AT_LEAST_12.
> 
> BR2_ARCH_HAS_NO_TOOLCHAIN_BUILDROOT is selected temporary
> and it's going to be rmoved after we gain libc support.
> 
> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>

I tested this series more extensively in the past weeks with 500+
Buildroot packages. Overall, this new architecture support looks good,
so I am in favor to merge those patches.

Before I do so, I would like to point out that enabling a new
architecture in Buildroot is not "just" testing the new
defconfigs are building and booting. The autobuilder will start
generating random configs for this architecture, including
any packages that could be selected for it. As soon as we'll merge
those patches, I expect to see new build failures for this arch.

They will most likely show up in:
https://autobuild.buildroot.org/?arch=loongarch64

Since you are registering yourself as the architecture maintainer
in Buildroot, will you be able to help solving those package issues?

I expect the kind of package maintenance to be:
- fixing package bugs specific to the arch
   (including upstreaming those fixes)
- updating failing packages to new versions
   (if their upstream already include loongarch fixes)
- marking packages as unsupported for this arch,
   typically by introducing a _ARCH_SUPPORTS Kconfig which
   does not list this arch.

If you promise to help us doing this maintenance, I think we could
this series merged soon.

What do you think?

Best regards,

Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot