On Mon, 13 Jan 2025 at 11:12, Thomas Schwinge <tschwi...@baylibre.com> wrote: > > Hi! > > On 2025-01-13T11:04:50+0000, Jonathan Wakely <jwak...@redhat.com> wrote: > > On Mon, 13 Jan 2025 at 11:03, Thomas Schwinge <tschwi...@baylibre.com> > > wrote: > >> On 2025-01-12T08:38:05+0100, Torbjorn SVENSSON > >> <torbjorn.svens...@foss.st.com> wrote: > >> > On 2025-01-12 01:05, Jonathan Wakely wrote: > >> >> On Mon, 23 Dec 2024, 19:05 Torbjörn SVENSSON, > >> >> <torbjorn.svens...@foss.st.com <mailto:torbjorn.svens...@foss.st.com>> > >> >> wrote: > >> >> > >> >> Ok for trunk and releases/gcc-14? > >> >> > >> >> OK > >> > > >> > Pushed as r15-6828-g4b0ef49d02f and r14.2.0-680-gd82fc939f91. > >> > >> On a configuration where libatomic does get built, I see (with standard > > > > Does *not* get built? > > No, *does* get built, and thus the PASS -> UNSUPPORTED is a regression.
Oh right! I misunderstood the problem, sorry. So we need the init so that libatomic_available actually works.
