public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/113202] std::find does not work with the maximum range of pointers Date: Wed, 03 Jan 2024 11:19:00 +0000 [thread overview] Message-ID: <bug-113202-4-5ES8XR6Lrf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113202-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113202 --- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> --- s + OFFSET has undefined behaviour. With -O2 or -O3 GCC even tells you where the problem is: find_bug.cpp: In function 'int main(int, char**)': find_bug.cpp:39:61: warning: array subscript 1048576 is outside array bounds of 'const char [6]' [-Warray-bounds=] 39 | std::cout << "strlen = " << strlen_no_ranges(s, s + OFFSET) << ", no ranges, OFFSET = " << OFFSET << std::endl; | ^ find_bug.cpp:40:58: warning: array subscript 1048576 is outside array bounds of 'const char [6]' [-Warray-bounds=] 40 | std::cout << "strlen = " << strlen_ranges(s, s + OFFSET) << ", ranges, OFFSET = " << OFFSET << std::endl; |
next prev parent reply other threads:[~2024-01-03 11:19 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-02 16:22 [Bug libstdc++/113202] New: " carsten.schmidt-achim at gmx dot de 2024-01-02 16:23 ` [Bug libstdc++/113202] " carsten.schmidt-achim at gmx dot de 2024-01-02 16:23 ` carsten.schmidt-achim at gmx dot de 2024-01-02 16:24 ` carsten.schmidt-achim at gmx dot de 2024-01-02 16:26 ` carsten.schmidt-achim at gmx dot de 2024-01-02 16:43 ` pinskia at gcc dot gnu.org 2024-01-03 9:59 ` carsten.schmidt-achim at gmx dot de 2024-01-03 10:08 ` pinskia at gcc dot gnu.org 2024-01-03 10:14 ` pinskia at gcc dot gnu.org 2024-01-03 10:16 ` xry111 at gcc dot gnu.org 2024-01-03 10:20 ` xry111 at gcc dot gnu.org 2024-01-03 11:19 ` redi at gcc dot gnu.org [this message] 2024-01-03 11:22 ` redi at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-113202-4-5ES8XR6Lrf@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).