aboutsummaryrefslogtreecommitdiff
path: root/gcc
diff options
context:
space:
mode:
authorJonathan Wakely <jwakely@redhat.com>2021-12-17 17:58:09 +0000
committerJonathan Wakely <jwakely@redhat.com>2022-01-05 13:47:00 +0000
commit9a2451c1013c21e76da89df89c3c8e5e6afe6154 (patch)
tree616b8ac2ce33d6f7f449761a8471d8f4404f08c9 /gcc
parent260a5334ee963f66745d0cb98316ee831737b22d (diff)
downloadgcc-9a2451c1013c21e76da89df89c3c8e5e6afe6154.zip
gcc-9a2451c1013c21e76da89df89c3c8e5e6afe6154.tar.gz
gcc-9a2451c1013c21e76da89df89c3c8e5e6afe6154.tar.bz2
libstdc++: Compare match_results for failed regex_match
The regex_match_debug testsuite helper doesn't compare the std::match_results objects after a failed match, but it should do. The standard says that the effects of a failed match on the match-results are unspecified, except that [conditions testable by operator==]. So we can check that the two sets of results compare equal even if the match failed. libstdc++-v3/ChangeLog: * testsuite/util/testsuite_regex.h (regex_match_debug): Compare results even if the match failed.
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions