From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Frager, Neal" <neal.frager@amd.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>,
"giulio.benetti@benettiengineering.com"
<giulio.benetti@benettiengineering.com>,
"ju.o@free.fr" <ju.o@free.fr>,
"romain.naour@gmail.com" <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH v1 1/1] package/gcc: add microblaze atomic support
Date: Tue, 5 Aug 2025 10:09:53 +0200 [thread overview]
Message-ID: <20250805100953.380f13df@windsurf> (raw)
In-Reply-To: <SA1PR12MB5615611A10ADA56A9816AAB7F022A@SA1PR12MB5615.namprd12.prod.outlook.com>
Hello Neal,
On Tue, 5 Aug 2025 07:29:52 +0000
"Frager, Neal" <neal.frager@amd.com> wrote:
> I have followed your steps and I see the same issue with gcc-15. It seems like
> a different issue. If you remove the atomic test and set patch from gcc-15.1.0
> and do the same build, you will see the exact same qemu boot failure.
Oh yes, I definitely didn't mean to imply that the issue was related to
the atomic fix. As you say, the defconfig can be built with GCC 15.x
without the atomic fix.
> So it seems like we have another issue with microblaze that appears with
> gcc-15...
Absolutely :-)
Not sure where to start to figure out what's going on. Perhaps run init
under strace? Or maybe build a working system with gcc 14.x, with one
executable in in built with gcc 15.x, and see if it works?
Thomas
--
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
next prev parent reply other threads:[~2025-08-05 8:10 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
2025-08-05 7:29 ` Frager, Neal via buildroot
2025-08-05 8:09 ` Thomas Petazzoni via buildroot [this message]
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=20250805100953.380f13df@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