diff options
| author | Jason Merrill <jason@redhat.com> | 2021-12-10 11:21:50 -0500 |
|---|---|---|
| committer | Jason Merrill <jason@redhat.com> | 2021-12-10 23:58:13 -0500 |
| commit | 2e8067041d1d69da02bd7578f58abc11eb35a04b (patch) | |
| tree | 5b3b28b4f30f602d6f8e96592a560f9803b3e08d /libgcc | |
| parent | 0bceef1671adee52e9cc409d82e5f5590fed8d45 (diff) | |
| download | gcc-2e8067041d1d69da02bd7578f58abc11eb35a04b.zip gcc-2e8067041d1d69da02bd7578f58abc11eb35a04b.tar.gz gcc-2e8067041d1d69da02bd7578f58abc11eb35a04b.tar.bz2 | |
libstdc++: check length in string append [PR103534]
In the testcase for 103534 we get a warning about append leading to memcpy
of a very large number of bytes overflowing the buffer. This turns out to
be because we weren't calling _M_check_length for string append. Rather
than do that directly, let's go through the public pointer append that calls
it.
PR c++/103534
libstdc++-v3/ChangeLog:
* include/bits/basic_string.h (append (basic_string)): Call pointer
append instead of _M_append directly.
gcc/testsuite/ChangeLog:
* g++.dg/warn/Wstringop-overflow-8.C: New test.
Diffstat (limited to 'libgcc')
0 files changed, 0 insertions, 0 deletions