https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109344
--- Comment #4 from albin <albin at yahoo dot com> --- Thanks for the info. If it was fixed three years ago how come it is still seen when using gcc (trunk) on Compiler Explorer? Is Compiler Explorer using an obsolete glibc?