public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/59048] std::string operator== between std::string and const char* creates unecessary temporary object Date: Fri, 08 Nov 2013 11:37:00 -0000 [thread overview] Message-ID: <bug-59048-4-0wlDJ4KptX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59048-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59048 --- Comment #4 from Paolo Carlini <paolo.carlini at oracle dot com> --- Indeed, I had a look to f and the correct operator== and compare are called, no temporaries. By the way, type_traits<char> uses memcmp not strcmp.
next prev parent reply other threads:[~2013-11-08 11:37 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-08 10:59 [Bug c++/59048] New: " luca.stoppa at bbh dot com 2013-11-08 11:12 ` [Bug libstdc++/59048] " redi at gcc dot gnu.org 2013-11-08 11:18 ` redi at gcc dot gnu.org 2013-11-08 11:34 ` luca.stoppa at bbh dot com 2013-11-08 11:37 ` paolo.carlini at oracle dot com [this message] 2013-11-08 11:41 ` luca.stoppa at bbh dot com 2013-11-08 11:46 ` paolo.carlini at oracle dot com 2013-11-08 11:46 ` redi at gcc dot gnu.org 2013-11-08 11:50 ` paolo.carlini at oracle dot com 2013-11-08 13:48 ` luca.stoppa at bbh dot com 2013-11-08 19:24 ` glisse at gcc dot gnu.org 2015-06-02 22:49 ` [Bug libstdc++/59048] operator== between std::string and const char* slower than strcmp neleai at seznam dot cz 2015-06-03 6:34 ` manu at gcc dot gnu.org 2015-06-03 7:54 ` glisse at gcc dot gnu.org 2021-02-11 20:08 ` hiraditya at msn dot com 2021-02-12 14:48 ` redi at gcc dot gnu.org 2022-06-14 15:15 ` redi at gcc dot gnu.org 2022-06-14 20:19 ` cvs-commit at gcc dot gnu.org 2022-06-14 20:21 ` 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-59048-4-0wlDJ4KptX@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).