public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/114822] New: ldist should produce memcpy/memset/memmove histograms based on loop information converted Date: Tue, 23 Apr 2024 09:44:36 +0000 [thread overview] Message-ID: <bug-114822-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114822 Bug ID: 114822 Summary: ldist should produce memcpy/memset/memmove histograms based on loop information converted Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: hubicka at gcc dot gnu.org Target Milestone: --- When loop is converted to string builtin we lose information about its size. This means that we won't expand it inline when the block size is expected to be small. This causes performance problem i.e. on std::vector and testcase from PR114821 which at least with profile feedback runs significantly slower than variant where memcpy is produced early #include <vector> typedef unsigned int uint32_t; int pair; void test() { std::vector<int> stack; stack.push_back (pair); while (!stack.empty()) { int cur = stack.back(); stack.pop_back(); if (true) { cur++; stack.push_back (cur); stack.push_back (cur); } if (cur > 10000) break; } } int main() { for (int i = 0; i < 10000; i++) test(); }
reply other threads:[~2024-04-23 9:44 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-114822-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).