public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/96780] debuginfo for std::move and std::forward isn't useful Date: Wed, 09 Mar 2022 15:34:28 +0000 [thread overview] Message-ID: <bug-96780-4-7r104zzLDO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96780-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96780 --- Comment #12 from Patrick Palka <ppalka at gcc dot gnu.org> --- I should mention I noticed a significant reduction in compile time, memory usage and unstripped object file size in some cases with the proposed patch at https://gcc.gnu.org/pipermail/gcc-patches/2022-March/591091.html. For instance, for the range-v3 test file test/algorithm/set_symmetric_difference4.cpp compiled with -O2 -g and a non-checking compiler, compile time/GC allocations/object file size decreases from 8.29s/551M/3508K to 8.00s/541M/3104K. The object file size decrease (naively measured with du) here is particularly surprising, nearly a 12% decrease. I suppose this means debug info for inlined calls to std::move/forward accounts for >=12% of the debug info size, which we no longer emit with the patch.
next prev parent reply other threads:[~2022-03-09 15:34 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-25 12:08 [Bug c++/96780] New: " redi at gcc dot gnu.org 2020-08-25 12:35 ` [Bug c++/96780] " mpolacek at gcc dot gnu.org 2020-09-12 16:05 ` ppalka at gcc dot gnu.org 2020-09-12 16:09 ` ppalka at gcc dot gnu.org 2021-04-06 13:44 ` redi at gcc dot gnu.org 2021-11-03 21:14 ` ppalka at gcc dot gnu.org 2021-11-03 23:17 ` redi at gcc dot gnu.org 2022-01-05 13:55 ` ppalka at gcc dot gnu.org 2022-01-05 16:11 ` jakub at gcc dot gnu.org 2022-03-01 19:12 ` vittorio.romeo at outlook dot com 2022-03-01 20:06 ` redi at gcc dot gnu.org 2022-03-03 9:15 ` redi at gcc dot gnu.org 2022-03-09 14:35 ` jason at gcc dot gnu.org 2022-03-09 14:35 ` jason at gcc dot gnu.org 2022-03-09 15:34 ` ppalka at gcc dot gnu.org [this message] 2022-03-09 17:12 ` redi at gcc dot gnu.org 2022-03-09 17:20 ` redi at gcc dot gnu.org 2022-03-10 4:33 ` jason at gcc dot gnu.org 2022-03-16 12:26 ` cvs-commit at gcc dot gnu.org 2022-03-26 23:37 ` jason at gcc dot gnu.org 2023-08-02 14:34 ` moncef.mechri at gmail dot com
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-96780-4-7r104zzLDO@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).