On Sun, 2019 Nov 17 22:41-05:00, Bruno Haible wrote:
>
> > * C11 _Thread_local support is utterly broken (test-thread_local
> > fails)
>
> I agree that these are bugs that are best discussed with the vendor.
>
> Should we add a workaround to the "check whether _Thread_local works"
> autoconf test, hardwiring the 'defined __MVS__' condition?
I do trust that this will start working at some point (IBM can't leave
it like this forever), so testing the functionality without assuming
anything for the system seems like a good status quo.
There is one bit that left me scratching my head, however. If I drop
-qlanglvl=extc99 from my CFLAGS (on the notion that the configure script
should find this flag itself), I see this result:
checking for xlc-wrap option to enable C11 features... unsupported
checking for xlc-wrap option to enable C99 features... -qlanglvl=extc1x
Is it proper for _AC_PROG_CC_C99() to try a C11 flag to get C99 mode?
This may yield C99 functionality, but __STDC_VERSION__ still indicates
C11, and applications taking this at face value will run into problems
if they attempt to use certain aspects of C11.
As far as I've seen, the C99 mode on this compiler (per my original
flag) is complete and functional.
--Daniel
--
Daniel Richard G. || sk...@iskunk.org
My ASCII-art .sig got a bad case of Times New Roman.
