Use SCANF_ISOC99_A instead of _IO_FLAGS2_SCANF_STD.
commitb87eb3f8feb826ac48463f598fc10476055bee5a
authorZack Weinberg <zackw@panix.com>
Wed, 7 Mar 2018 19:31:59 +0000 (7 14:31 -0500)
committerGabriel F. T. Gomes <gabriel@inconstante.eti.br>
Wed, 5 Dec 2018 20:15:42 +0000 (5 18:15 -0200)
treef71f60fbd1a5340ca8d2a9015c813b04cf053036
parent349718d4d7841df46bcc36df9bc2baef4c40d6f5
Use SCANF_ISOC99_A instead of _IO_FLAGS2_SCANF_STD.

Change the callers of __vfscanf_internal and __vfwscanf_internal that
want C99-compliant behavior to communicate this via the new flags
argument, rather than setting bits on the FILE object.  This also
means these functions do not need to do their own locking.

Tested for powerpc and powerpc64le.
16 files changed:
ChangeLog
libio/libio.h
libio/libioP.h
stdio-common/isoc99_fscanf.c
stdio-common/isoc99_scanf.c
stdio-common/isoc99_sscanf.c
stdio-common/isoc99_vfscanf.c
stdio-common/isoc99_vscanf.c
stdio-common/isoc99_vsscanf.c
stdio-common/vfscanf-internal.c
wcsmbs/isoc99_fwscanf.c
wcsmbs/isoc99_swscanf.c
wcsmbs/isoc99_vfwscanf.c
wcsmbs/isoc99_vswscanf.c
wcsmbs/isoc99_vwscanf.c
wcsmbs/isoc99_wscanf.c