https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123193
Thiago Jung Bauermann <thiago.bauermann at linaro dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |thiago.bauermann at linaro dot
org
--- Comment #7 from Thiago Jung Bauermann <thiago.bauermann at linaro dot org>
---
(In reply to Jonathan Wakely from comment #5)
>
>
> (In reply to Christophe Lyon from comment #0)
> > Linaro CI has detected a failure in g++.dg/modules/compile-std1.C on some
> > arm configurations:
> > --target arm-eabi --disable-multilib --with-mode=thumb --with-cpu=cortex-m7
> > --with-float=hard
> >
> > and
> > --target arm-eabi --disable-multilib --with-mode=arm --with-arch=armv7-a
> > --with-fpu=vfpv3-d16 --with-float=softfp
> >
> > ⋮
>
> All the errors above are guarded with:
>
> #if _GLIBCXX_USE_STDIO_LOCKING && _GLIBCXX_USE_GLIBC_STDIO_EXT
>
> which should not be true for arm-none-eabi. Even the usual "newlib declares
> everything then fails at link time" problem shouldn't cause these errors. I
> don't know what's happening here.
>
>
> I think all the other errors should have been fixed by
> r16-5939-gda97de41f8837a
>
>
> Is this still failing for Linaro CI?
It's not. I can confirm that g++.dg/modules/compile-std1.C is now fully passing
in the Linaro CI. Thank you!
