https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118280
--- Comment #33 from Neal Frager <neal.frager at amd dot com> --- (In reply to Álvaro "G. M." from comment #32) > (In reply to Neal Frager from comment #18) > > I have raised this issue internally, as I think it would be good for us to > > fix it. > > > > I definitely do not think this issue is worth deprecating microblaze support > > in gcc. To be honest, the majority of the microblaze usage I am aware of is > > simple microcontroller state machine code. Meaning bare-metal c code. > > > > I believe this is why fixing the issue has not come up from the community as > > I am not sure many microblaze users are using c++, so they are not seeing > > this problem. > > > > Hi, > > Just wanted to chime in: I (at the company I work for) are actively using > Linux on microblaze. As of today, we are in the process of manufacturing a > series of about 500 units of an in-house designed PCB that relies on Linux > running on top of Microblaze. I've been finding some problems lately > migrating from a 2016 version of buildroot, which used gcc-5.4.0, to a 2025 > release, which now uses modern gcc. > > Just wanted to say thanks to all of you guys still maintaining this. It > looks like AMD/Xilinx isn't much interested, but for me it would be a great > pain having to switch to another soft-cpu. Although I guess the future for > me is microblaze-v, it still doesn't have an MMU, so the port is not > immediate for me. > > Best regards Hi Alvaro, Just to clarify, you are right that our long term solution is to move to Microblaze-V (RISC-V). While we had good reasons for developing Microblaze, we believe open cores are the better solution moving forward. The idea of Microblaze-V is that we keep all the IPs, interrupt controller solution and peripherals, such that you can literally migrate from Microblaze to Microblaze-V by only changing the toolchain from microblaze to risc-v. Peripherals and register addressing will remain the same. We are not far from enabling Linux on our Microblaze-V core, and you can expect to see this in our 2026.x releases. In spite of all this, we are keeping Microblaze going for companies such as yours, so you have time to make the transition to Microblaze-V. You can expect that the GCC toolchain will still get fixed should new bugs be found, but we will not be doing any new active development for the Microblaze. If you apply the following two patches to GCC-15, you can use the latest GCC v15.2.0 to build Linux running on the Microblaze, so you can indeed update to the latest toolchain version. The first of these two patches has already been committed upstream. The second is a work around solution with development in progress. https://github.com/buildroot/buildroot/blob/master/package/gcc/15.2.0/0002-MicroBlaze-Enhance-support-for-atomics.-Fix-PR118280.patch https://github.com/buildroot/buildroot/blob/master/package/gcc/15.2.0/0003-gcc-config-microblaze-fix-ira-for-GCC15.patch Best regards, Neal Frager AMD
