Specifically, the test std/input.output/string.streams/stringstream/stringstream.members/gcount.pass.cpp allocates a std::string with INT_MAX-1 elements, and then writes this to a std::stringstream. On Linux, running this test consumes around 5.0 GB of memory; on Windows, it ends up using up to 6.8 GB of memory. This limits whether such tests can run on e.g. GitHub Actions runners, where the free runners are limited to 8 GB of memory. This is somewhat similar to, but still notably different, from the existing test parameter long_tests.
38 lines
1.0 KiB
C++
38 lines
1.0 KiB
C++
//===----------------------------------------------------------------------===//
|
|
//
|
|
// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
|
|
// See https://llvm.org/LICENSE.txt for license information.
|
|
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
|
|
//
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
// UNSUPPORTED: 32-bit-pointer
|
|
// REQUIRES: large_tests
|
|
|
|
// Test that tellp() does not break the stringstream after INT_MAX, due to use
|
|
// of pbump() that accept int.
|
|
|
|
#include <cassert>
|
|
#include <climits>
|
|
#include <sstream>
|
|
#include <string>
|
|
|
|
int main(int, char**) {
|
|
std::stringstream ss;
|
|
std::string payload(INT_MAX - 1, '\0');
|
|
|
|
ss.write(payload.data(), payload.size());
|
|
assert(ss.tellp() == INT_MAX - 1);
|
|
|
|
ss.write("a", 1);
|
|
assert(ss.tellp() == INT_MAX);
|
|
|
|
ss.write("b", 1);
|
|
assert(ss.tellp() == INT_MAX + 1ULL);
|
|
// it fails only after previous tellp() corrupts the internal field with int
|
|
// overflow
|
|
assert(ss.tellp() == INT_MAX + 1ULL);
|
|
|
|
return 0;
|
|
}
|