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 tree-optimization/62156] memcmp doesn't see through memcpy at compile-time Date: Mon, 18 Aug 2014 15:19:00 -0000 [thread overview] Message-ID: <bug-62156-4-oCYb6RpxQA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-62156-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62156 --- Comment #3 from Marc Glisse <glisse at gcc dot gnu.org> --- Not much difference using __gnu_cxx::__vstring (no reference counting, small string optimization): __builtin_memcpy (&MEM[(struct __sso_string_base *)&D.28720].D.23707._M_local_data, "foo", 3); MEM[(size_type *)&D.28720 + 8B] = 3; MEM[(char_type &)&D.28720 + 19] = 0; __r_46 = __builtin_memcmp (&MEM[(struct __sso_string_base *)&D.28720].D.23707._M_local_data, "bar", 3);
next prev parent reply other threads:[~2014-08-18 15:19 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-15 11:36 [Bug tree-optimization/62156] New: " glisse at gcc dot gnu.org 2014-08-18 14:06 ` [Bug tree-optimization/62156] " rguenth at gcc dot gnu.org 2014-08-18 14:47 ` glisse at gcc dot gnu.org 2014-08-18 15:19 ` glisse at gcc dot gnu.org [this message] 2014-08-19 8:02 ` rguenther at suse dot de 2014-08-19 11:15 ` glisse at gcc dot gnu.org 2014-08-19 11:19 ` rguenther at suse dot de
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-62156-4-oCYb6RpxQA@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).