public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "michael.haubenwallner at salomon dot at" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/54392] [4.6/4.7/4.8 Regression] std::string::assign() fails to update length Date: Wed, 29 Aug 2012 10:50:00 -0000 [thread overview] Message-ID: <bug-54392-4-JTZE1Jwk8Y@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54392-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54392 --- Comment #4 from Michael Haubenwallner <michael.haubenwallner at salomon dot at> 2012-08-29 10:50:22 UTC --- (In reply to comment #0) Extending the testcase shows even more bad behavior in 4.4.3 and earlier: #include <string> #include <cassert> int main() { std::string s1, s2; s1.assign(s2.c_str(), 1); assert( s1.size() == 1 ); std::string s3; assert( s3.size() == 0 ); // up to gcc-4.4.3 fail here }
next prev parent reply other threads:[~2012-08-29 10:50 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-28 13:42 [Bug libstdc++/54392] New: [4.6/4.7/4.8 Regression] std::string::append() " redi at gcc dot gnu.org 2012-08-28 18:03 ` [Bug libstdc++/54392] " hjl.tools at gmail dot com 2012-08-28 18:10 ` redi at gcc dot gnu.org 2012-08-29 7:36 ` [Bug libstdc++/54392] [4.6/4.7/4.8 Regression] std::string::assign() " redi at gcc dot gnu.org 2012-08-29 10:50 ` michael.haubenwallner at salomon dot at [this message] 2012-08-29 14:16 ` paolo.carlini at oracle dot com 2012-08-29 14:47 ` paolo.carlini at oracle dot com 2012-08-29 15:14 ` paolo.carlini at oracle dot com 2012-08-29 15:21 ` michael.haubenwallner at salomon dot at 2012-08-29 15:29 ` paolo.carlini at oracle dot com 2012-08-29 15:33 ` paolo.carlini at oracle dot com 2012-08-29 16:21 ` paolo.carlini at oracle dot com 2012-08-29 16:53 ` paolo.carlini at oracle dot com 2012-08-29 23:21 ` paolo.carlini at oracle dot com 2012-08-30 7:33 ` michael.haubenwallner at salomon dot at 2012-08-31 16:52 ` paolo.carlini at oracle dot com 2012-09-06 14:44 ` rguenth at gcc dot gnu.org 2012-09-07 10:45 ` rguenth at gcc dot gnu.org 2013-01-11 15:58 ` jakub at gcc dot gnu.org 2013-01-11 16:01 ` paolo.carlini at oracle dot com 2013-01-11 16:04 ` paolo.carlini at oracle dot com 2013-01-11 18:59 ` redi at gcc dot gnu.org 2013-01-31 10:06 ` paolo.carlini at oracle dot com 2013-04-12 15:17 ` [Bug libstdc++/54392] [4.7/4.8/4.9 " jakub at gcc dot gnu.org 2014-03-04 11:45 ` jakub at gcc dot gnu.org 2014-03-04 12:02 ` redi at gcc dot gnu.org 2014-06-12 13:48 ` [Bug libstdc++/54392] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-09-19 13:26 ` [Bug libstdc++/54392] [4.8/4.9/5 " redi at gcc dot gnu.org 2014-12-22 13:51 ` 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-54392-4-JTZE1Jwk8Y@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).