diff options
| author | Jonathan Wakely <jwakely@redhat.com> | 2020-05-04 21:13:28 +0100 |
|---|---|---|
| committer | Jonathan Wakely <jwakely@redhat.com> | 2020-05-04 22:47:30 +0100 |
| commit | bb27781b64162e1769df15e0c97e8d2145d2d10d (patch) | |
| tree | 2c34c125e8275c26ac0ab02ca7b42ab2ad7bbd35 /gcc/tree-vectorizer.c | |
| parent | cc7e4de998cd2a31eb7c834fd427e7f16a99d60a (diff) | |
| download | gcc-bb27781b64162e1769df15e0c97e8d2145d2d10d.zip gcc-bb27781b64162e1769df15e0c97e8d2145d2d10d.tar.gz gcc-bb27781b64162e1769df15e0c97e8d2145d2d10d.tar.bz2 | |
libstdc++: Fix incorrect size calculation in PMR resource (PR 94906)
Calculating the size of a chunk being returned to the upstream allocator
was done with a 32-bit type, so it wrapped if the chunk was 4GB or
larger.
I don't know how to test this without allocating 4GB, so there's no test
in the testsuite. It has been tested manually with allocations sizes and
alignments exceeding 4GB.
PR libstdc++/94906
* src/c++17/memory_resource.cc
(monotonic_buffer_resource::_Chunk::release): Use size_t for shift
operands.
Diffstat (limited to 'gcc/tree-vectorizer.c')
0 files changed, 0 insertions, 0 deletions