https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118280
Álvaro "G. M." <alvaro.gamez at hazent dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alvaro.gamez at hazent dot com
--- Comment #32 from Álvaro "G. M." <alvaro.gamez at hazent dot com> ---
(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
