aboutsummaryrefslogtreecommitdiff
path: root/gcc/cp/constexpr.cc
diff options
context:
space:
mode:
authorAlexandre Oliva <oliva@adacore.com>2023-03-03 15:59:33 -0300
committerAlexandre Oliva <oliva@gnu.org>2023-03-03 16:06:46 -0300
commit8be49eb927e1e65a715bc6eb73b9ce271c8b24c2 (patch)
treedd2f3e9629770df50a61081612fab7debd195279 /gcc/cp/constexpr.cc
parent21edd841611a97442a6b95e8ec7e91ff8fd3a451 (diff)
downloadgcc-8be49eb927e1e65a715bc6eb73b9ce271c8b24c2.zip
gcc-8be49eb927e1e65a715bc6eb73b9ce271c8b24c2.tar.gz
gcc-8be49eb927e1e65a715bc6eb73b9ce271c8b24c2.tar.bz2
[libstdc++] [prettyprint] add local std::string use to more tests
We're getting regressions after ugprading to GDB 13 in a few of the libstdc++ pretty-printing tests. It might seem like a GDB regression, but that update has a new symbol reader, and Tom Tromey says it exposes a latent problem in the pretty-printer, namely, when a name is not defined locally in the local translation unit, GDB will look for it in other units, and if multiple different definitions are available, there are no guarantees as to which one it will find. Since libstdc++ contains units in which std::string maps to different types, in order to ensure the tests get the std::string definition we expect, we need std::string to be present in the debug information for the test itself, as we already do in other tests. for libstdc++-v3/ChangeLog * testsuite/libstdc++-prettyprinters/80276.cc: Add std::string to debug info. * testsuite/libstdc++-prettyprinters/libfundts.cc: Likewise.
Diffstat (limited to 'gcc/cp/constexpr.cc')
0 files changed, 0 insertions, 0 deletions