diff options
| author | Florian Weimer <fweimer@redhat.com> | 2022-08-18 08:49:54 +0200 |
|---|---|---|
| committer | Florian Weimer <fweimer@redhat.com> | 2022-12-12 15:38:32 +0100 |
| commit | 9e6084af5260c144509be67a906696db99dc5ddf (patch) | |
| tree | fc42731f860d6971fb40baa337029f5ee03f99b8 /malloc/alloc_buffer_alloc_array.c | |
| parent | c0dee012ab097481adfd3826e83a84decd0f87a2 (diff) | |
| download | glibc-9e6084af5260c144509be67a906696db99dc5ddf.tar.xz glibc-9e6084af5260c144509be67a906696db99dc5ddf.zip | |
stdio-common: Introduce buffers for implementing printf
These buffers will eventually be used instead of FILE * objects
to implement printf functions. The multibyte buffer is struct
__printf_buffer, the wide buffer is struct __wprintf_buffer.
To enable writing type-generic code, the header files
printf_buffer-char.h and printf_buffer-wchar_t.h define the
Xprintf macro differently, enabling Xprintf (buffer) to stand
for __printf_buffer and __wprintf_buffer as appropriate. For
common cases, macros like Xprintf_buffer are provided as a more
syntactically convenient shortcut.
Buffer-specific flush callbacks are implemented with a switch
statement instead of a function pointer, to avoid hardening issues
similar to those of libio vtables. struct __printf_buffer_as_file
is needed to support custom printf specifiers because the public
interface for that requires passing a FILE *, which is why there
is a trapdoor back from these buffers to FILE * streams.
Since the immediate user of these interfaces knows when processing
has finished, there is no flush callback for the end of processing,
only a flush callback for the intermediate buffer flush.
Diffstat (limited to 'malloc/alloc_buffer_alloc_array.c')
0 files changed, 0 insertions, 0 deletions
