On Tue, 2024-09-24 at 12:54 +0100, Alex Bennée wrote: > Ilya Leoshkevich <i...@linux.ibm.com> writes: > > (add Mahesh to CC) > > > GCC produces invalid code for microblaze atomics. > > > > The fix is unfortunately not upstream, so fetch it from an external > > location and apply it locally. > > Queued to testing/next, thanks. > > However I didn't see any tests failing so I'm curious where you saw > the > problem? Would it be worth adding an atomics test (microblaze or > generic) to catch this?
It's very reliably caught by the new test that I'm proposing as a part of this series: https://lore.kernel.org/qemu-devel/20240923162208.90745-19-...@linux.ibm.com/T/#u > > Also for the Microblaze guys is there any push to upstream the > patches > you have into GCC or have an easily distributively binary build we > could > convert our dockerfiles to? > > > > > Suggested-by: Peter Maydell <peter.mayd...@linaro.org> > > Signed-off-by: Ilya Leoshkevich <i...@linux.ibm.com> > > --- > > .../debian-microblaze-cross.d/build-toolchain.sh | 8 > > ++++++++ > > tests/docker/dockerfiles/debian-toolchain.docker | 7 > > +++++++ > > 2 files changed, 15 insertions(+)
