public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kip at thevertigo dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/99402] [10/11 Regression] std::copy creates _GLIBCXX_DEBUG false positive for attempt to subscript a dereferenceable (start-of-sequence) iterator Date: Fri, 05 Mar 2021 20:00:16 +0000 [thread overview] Message-ID: <bug-99402-4-bm0T4tjDHz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99402-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99402 --- Comment #8 from Kip Warner <kip at thevertigo dot com> --- And for anyone finding this from a search engine, the temporary workaround is to use std::copy_n.
next prev parent reply other threads:[~2021-03-05 20:00 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-05 9:09 [Bug c++/99402] New: " kip at thevertigo dot com 2021-03-05 12:16 ` [Bug libstdc++/99402] [10/11 Regression] " redi at gcc dot gnu.org 2021-03-05 12:30 ` redi at gcc dot gnu.org 2021-03-05 12:33 ` redi at gcc dot gnu.org 2021-03-05 12:40 ` redi at gcc dot gnu.org 2021-03-05 12:55 ` redi at gcc dot gnu.org 2021-03-05 12:59 ` redi at gcc dot gnu.org 2021-03-05 19:26 ` fdumont at gcc dot gnu.org 2021-03-05 20:00 ` kip at thevertigo dot com [this message] 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2021-04-08 12:53 ` rguenth at gcc dot gnu.org 2021-04-13 20:51 ` [Bug libstdc++/99402] [10 " redi at gcc dot gnu.org 2021-04-13 22:19 ` kip at thevertigo dot com 2021-04-13 22:45 ` redi at gcc dot gnu.org 2021-04-23 12:02 ` fdumont at gcc dot gnu.org 2021-04-23 13:04 ` 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-99402-4-bm0T4tjDHz@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).