[Bug libstdc++/91547] std::string_view find_last_not_of can trigger unsigned integer overflow

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91547 --- Comment #6 from Andrew Pinski --- (In reply to Vitali from comment #4) > FWIW clang does implement this. Even if the maintainers disagree on the > utility in practice, does feature parity for command-line options with Clang > change the

[Bug libstdc++/91547] std::string_view find_last_not_of can trigger unsigned integer overflow

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91547 --- Comment #5 from Vitali --- https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html

[Bug libstdc++/91547] std::string_view find_last_not_of can trigger unsigned integer overflow

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91547 Vitali changed: What|Removed |Added CC||vlovich at gmail dot com --- Comment #4 from

[Bug libstdc++/91547] std::string_view find_last_not_of can trigger unsigned integer overflow

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91547 --- Comment #3 from Mateusz Szychowski --- > The behaviour of that function is perfectly well defined. > Yes because it is not useful and causes to print when there is no bug at all > and wrapping behavior is expected. It was a decison that

[Bug libstdc++/91547] std::string_view find_last_not_of can trigger unsigned integer overflow

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91547 --- Comment #2 from Andrew Pinski --- >I don't think that GCC has '-fsanitizer=unsigned-integer-overflow' option Yes because it is not useful and causes to print when there is no bug at all and wrapping behavior is expected. It was a decison

[Bug libstdc++/91547] std::string_view find_last_not_of can trigger unsigned integer overflow

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91547 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---