public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/104719] Use of `std::move` in libstdc++ leads to worsened debug performance Date: Mon, 28 Feb 2022 17:24:27 +0000 [thread overview] Message-ID: <bug-104719-4-QKtgfzy2Xe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104719-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104719 --- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Vittorio Romeo from comment #4) > I like the idea of having the compiler itself fold calls to things like > `std::move` and `std::forward` as suggested in the linked > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96780. That benefits user code too, so that users won't have to use static_cast<T&&> in their own code because "std::move is slow". > But I think this issue I opened should be more general for any standard > library function that ends up impacting debug performance. Another common > example in the gamedev community is `std::vector`. Does the gamedev community actually use -Og though? Because if they only use -O0 (as is certainly the case for some) then the solution is "don't do that". Do they even use GCC/libstdc++ at all? Would they actually be more likely to if we change anything here? For those who are using -Og, adding always_inline to trivial accessors shouldn't be necessary, because GCC _should_ always inline them anyway. > In this benchmark, which uses `-Og`, you can notice a large performance > difference between a `std::vector<int>` and `int*` dynamic array for > operations that I believe should have equal performance: > - https://quick-bench.com/q/lrS4I-lmDJ3VFP8L8rG2YHGXO-8 > - https://quick-bench.com/q/Uf-t79n7uYWAKdThOL_wxSp12Y0 > > Are the above results also something that should be handled on the compiler > side of things? Or would, for example, marking `std::vector::operator[]` and > `std::vector::iterator::operator*` as `always_inline` remove the performance > discrepancy? Somebody will have to investigate whether lack of inlining is the problem there. My guess would be that it's not due to trivial functions like op[] failing to be inlined, and so always_inline wouldn't help (except at -O0, but "don't do that" if you need performance :-)
next prev parent reply other threads:[~2022-02-28 17:24 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-28 16:20 [Bug libstdc++/104719] New: " vittorio.romeo at outlook dot com 2022-02-28 16:46 ` [Bug libstdc++/104719] " redi at gcc dot gnu.org 2022-02-28 16:50 ` redi at gcc dot gnu.org 2022-02-28 16:56 ` egallager at gcc dot gnu.org 2022-02-28 17:00 ` vittorio.romeo at outlook dot com 2022-02-28 17:16 ` redi at gcc dot gnu.org 2022-02-28 17:20 ` vittorio.romeo at outlook dot com 2022-02-28 17:24 ` redi at gcc dot gnu.org [this message] 2022-02-28 17:37 ` redi at gcc dot gnu.org 2022-03-01 2:23 ` vittorio.romeo at outlook dot com 2022-03-01 20:12 ` redi at gcc dot gnu.org 2022-03-01 20:14 ` redi at gcc dot gnu.org 2022-03-10 23:04 ` jason at gcc dot gnu.org 2022-03-26 23:37 ` jason at gcc dot gnu.org 2022-03-27 7:35 ` redi at gcc dot gnu.org 2022-05-04 15:34 ` cvs-commit at gcc dot gnu.org 2022-05-04 15:34 ` cvs-commit at gcc dot gnu.org 2022-05-04 15:49 ` unlvsur at live dot com 2022-05-04 15:55 ` 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-104719-4-QKtgfzy2Xe@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).