Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@amd.com>
Cc: <buildroot@buildroot.org>,
	<giulio.benetti@benettiengineering.com>, <ju.o@free.fr>,
	<romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH v1 1/1] package/gcc: add microblaze atomic support
Date: Mon, 4 Aug 2025 21:40:47 +0200	[thread overview]
Message-ID: <20250804214047.5cfcf471@windsurf> (raw)
In-Reply-To: <20250728045145.132333-1-neal.frager@amd.com>

Hello Neal,

On Mon, 28 Jul 2025 05:51:45 +0100
Neal Frager via buildroot <buildroot@buildroot.org> wrote:

> This patch adds atomic test and set support for the microblaze arch.  A patch
> is required to use atomic test and set with gcc 14 and 15 which has been
> submitted upstream.
> 
> To test this patch with gcc 14:
> $ cat > .config<<EOF
> BR2_microblazeel=y
> BR2_GCC_VERSION_14_X=y
> BR2_TOOLCHAIN_BUILDROOT_CXX=y
> BR2_PACKAGE_ACPITOOL=y
> EOF
> $ make olddefconfig
> $ make
> 
> To test this patch with gcc 15:
> $ cat > .config<<EOF
> BR2_microblazeel=y
> BR2_GCC_VERSION_15_X=y
> BR2_TOOLCHAIN_BUILDROOT_CXX=y
> BR2_PACKAGE_ACPITOOL=y
> EOF
> $ make olddefconfig
> $ make
> 
> Fixes: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118280
> Upstream: https://patchwork.ozlabs.org/project/gcc/list/?series=466193
> 
> Signed-off-by: Neal Frager <neal.frager@amd.com>

Thanks a lot for this patch, which I have successfully tested, so:

Tested-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

However, there is now a separate problem: a build with gcc 14.x
generates a working user-space, but a build with gcc 15.x does not.

Try to build qemu_microblazeel_mmu_defconfig and then run it under qemu:

  ./output/host/bin/qemu-system-microblazeel -M petalogix-s3adsp1800 -kernel output/images/linux.bin -serial stdio

it works fine.

Now, change to GCC 15.x, rebuild from scratch, try again: the kernel
will boot, but the boot will stop at:

Run /init as init process
  with arguments:
    /init
  with environment:
    HOME=/
    TERM=linux

and never go further.

Any idea?

Thomas Petazzoni
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-08-04 19:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28  4:51 [Buildroot] [PATCH v1 1/1] package/gcc: add microblaze atomic support Neal Frager via buildroot
2025-08-04 19:40 ` Thomas Petazzoni via buildroot [this message]
2025-08-05  7:29   ` Frager, Neal via buildroot
2025-08-05  8:09     ` Thomas Petazzoni via buildroot
2025-08-05 10:31       ` Frager, Neal via buildroot
2025-08-05 10:58         ` Thomas Petazzoni via buildroot
2025-08-06 20:17           ` Thomas Petazzoni via buildroot
2025-08-07  4:49             ` Frager, Neal via buildroot
2025-08-11  7:31             ` Frager, Neal via buildroot
2025-08-11  8:12               ` Thomas Petazzoni via buildroot
2025-08-11  8:33                 ` Frager, Neal via buildroot
2025-08-11  9:22                   ` Peter Korsgaard
2025-08-21 19:20 ` Thomas Perale via buildroot

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=20250804214047.5cfcf471@windsurf \
    --to=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=ju.o@free.fr \
    --cc=neal.frager@amd.com \
    --cc=romain.naour@gmail.com \
    --cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox