public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/92442] Compiling Boost.Spirit.X3 code uses exuberant amount of RAM with -gpubnames
Date: Tue, 16 Mar 2021 11:59:14 +0000	[thread overview]
Message-ID: <bug-92442-4-tK92htXm2V@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92442-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92442

--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
Mark, you're looking after -gsplit-dwarf - can you comment on whether we can
drop the -gpubnames "requirement"?

In the end I'd suggest to change the implementation to emit pubnames from the
pruned DIE tree rather than gathering them upfront in various places and
make them prevent pruning DIEs.

  parent reply	other threads:[~2021-03-16 11:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-92442-4@http.gcc.gnu.org/bugzilla/>
2021-03-16 11:54 ` rguenth at gcc dot gnu.org
2021-03-16 11:59 ` rguenth at gcc dot gnu.org [this message]
2021-03-16 21:14 ` mark 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-92442-4-tK92htXm2V@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: link
Be 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).