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++/94353] std::copy* breaks when one type is volatile Date: Fri, 27 Mar 2020 09:21:21 +0000 [thread overview] Message-ID: <bug-94353-4-h8T8DxKGUS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94353-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94353 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- It is fixed by that commit, and there are several tests for mixed volatile pointers e.g. + volatile int i[2] = { 1, 2 }; + volatile int j[2] = { 0, 0 }; + int k[2] = { 0, 0 }; + + std::copy(i, i+2, j); + VERIFY( j[0] == 1 && j[1] == 2 ); + std::copy(i, i+2, k); ^^^^^^^^^^^^^^^^^^^^^ *** This bug has been marked as a duplicate of bug 94013 ***
prev parent reply other threads:[~2020-03-27 9:21 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-27 9:06 [Bug libstdc++/94353] New: " alex at grundis dot de 2020-03-27 9:21 ` redi at gcc dot gnu.org [this message]
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-94353-4-h8T8DxKGUS@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).