public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hewillk at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/100104] std::transform is 1.5 times faster than std::copy with -O3 Date: Sun, 18 Apr 2021 17:30:28 +0000 [thread overview] Message-ID: <bug-100104-4-vXwF1S7B4H@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100104-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100104 康桓瑋 <hewillk at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #5 from 康桓瑋 <hewillk at gmail dot com> --- After actually executing the same code on my local and remote servers, I did not produce such a result, so I think it should only be an issue of the environment, thank you for your time.
prev parent reply other threads:[~2021-04-18 17:30 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-15 18:06 [Bug c++/100104] New: " hewillk at gmail dot com 2021-04-15 19:30 ` [Bug middle-end/100104] " pinskia at gcc dot gnu.org 2021-04-16 1:42 ` hewillk at gmail dot com 2021-04-16 1:43 ` hewillk at gmail dot com 2021-04-16 1:51 ` hewillk at gmail dot com 2021-04-18 17:30 ` hewillk at gmail dot com [this message]
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-100104-4-vXwF1S7B4H@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).