public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/46830] s.swap(s) triggers overlapped memcpy() for versa_string Date: Tue, 07 Dec 2010 02:43:00 -0000 [thread overview] Message-ID: <bug-46830-4-xOf6yNLyfh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46830-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46830 --- Comment #2 from paolo at gcc dot gnu.org <paolo at gcc dot gnu.org> 2010-12-07 02:43:20 UTC --- Author: paolo Date: Tue Dec 7 02:43:16 2010 New Revision: 167528 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=167528 Log: 2010-12-06 Paul Pluzhnikov <ppluzhnikov@google.com> PR libstdc++/46830 * include/ext/sso_string_base.h (__sso_string_base<>::_M_swap): Early return when this == &__rcs. Modified: trunk/libstdc++-v3/ChangeLog trunk/libstdc++-v3/include/ext/sso_string_base.h
next prev parent reply other threads:[~2010-12-07 2:43 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-07 1:49 [Bug c++/46830] New: " ppluzhnikov at google dot com 2010-12-07 2:14 ` [Bug libstdc++/46830] " paolo.carlini at oracle dot com 2010-12-07 2:43 ` paolo at gcc dot gnu.org [this message] 2010-12-07 2:45 ` paolo.carlini at oracle dot com
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-46830-4-xOf6yNLyfh@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).