public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/62187] New: std::string==const char* could compare sizes first Date: Tue, 19 Aug 2014 13:21:00 -0000 [thread overview] Message-ID: <bug-62187-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62187 Bug ID: 62187 Summary: std::string==const char* could compare sizes first Product: gcc Version: 5.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: enhancement Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: glisse at gcc dot gnu.org Hello, when I compare 2 basic_string with ==, libstdc++ only uses the optimization of first checking that the sizes are the same (before calling compare) if __is_char<_CharT> and the traits and allocator are the default ones. I don't understand why, but assuming there is a good reason, I believe the optimization should still apply when comparing std::string and const char*. (this applies to __vstring as well) This was noticed in PR 62156, where we also see that std::string("foo") does a memcpy of size 3 then sets the 4th char to '\0', where a single memcpy of size 4 would make sense.
next reply other threads:[~2014-08-19 13:21 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-19 13:21 glisse at gcc dot gnu.org [this message] 2022-06-14 14:58 ` [Bug libstdc++/62187] " redi at gcc dot gnu.org 2022-06-14 20:19 ` cvs-commit at gcc dot gnu.org 2022-06-14 20:20 ` 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-62187-4@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).