| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To help detect common kinds of memory (and other resource) management
bugs, GCC 11 adds support for the detection of mismatched calls to
allocation and deallocation functions. At each call site to a known
deallocation function GCC checks the set of allocation functions
the former can be paired with and, if the two don't match, issues
a -Wmismatched-dealloc warning (something similar happens in C++
for mismatched calls to new and delete). GCC also uses the same
mechanism to detect attempts to deallocate objects not allocated
by any allocation function (or pointers past the first byte into
allocated objects) by -Wfree-nonheap-object.
This support is enabled for built-in functions like malloc and free.
To extend it beyond those, GCC extends attribute malloc to designate
a deallocation function to which pointers returned from the allocation
function may be passed to deallocate the allocated objects. Another,
optional argument designates the positional argument to which
the pointer must be passed.
This change is the first step in enabling this extended support for
Glibc.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* libio/Makefile (routines): Add wmemstream.
(tests): Add tst-memstream1, tst-memstream2, tst-wmemstream2, and
tst-wmemstream2.
* libio/tst-memstream1.c: New file.
* libio/tst-memstream2.c: New file.
* libio/tst-wmemstream1.c: New file.
* libio/tst-wmemstream2.c: New file.
* libio/memstream.c (_IO_mem_sync): Remove useless call to
_IO_default_sync.
|
