public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug debug/92442] Compiling Boost.Spirit.X3 code uses exuberant amount of RAM with -gpubnames
       [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
  2021-03-16 21:14 ` mark at gcc dot gnu.org
  2 siblings, 0 replies; 3+ messages in thread
From: rguenth at gcc dot gnu.org @ 2021-03-16 11:54 UTC (permalink / raw)
  To: gcc-bugs

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jeanmichael.celerier@gmail.
                   |                            |com

--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
*** Bug 93632 has been marked as a duplicate of this bug. ***

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug debug/92442] Compiling Boost.Spirit.X3 code uses exuberant amount of RAM with -gpubnames
       [not found] <bug-92442-4@http.gcc.gnu.org/bugzilla/>
  2021-03-16 11:54 ` [Bug debug/92442] Compiling Boost.Spirit.X3 code uses exuberant amount of RAM with -gpubnames rguenth at gcc dot gnu.org
@ 2021-03-16 11:59 ` rguenth at gcc dot gnu.org
  2021-03-16 21:14 ` mark at gcc dot gnu.org
  2 siblings, 0 replies; 3+ messages in thread
From: rguenth at gcc dot gnu.org @ 2021-03-16 11:59 UTC (permalink / raw)
  To: gcc-bugs

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.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug debug/92442] Compiling Boost.Spirit.X3 code uses exuberant amount of RAM with -gpubnames
       [not found] <bug-92442-4@http.gcc.gnu.org/bugzilla/>
  2021-03-16 11:54 ` [Bug debug/92442] Compiling Boost.Spirit.X3 code uses exuberant amount of RAM with -gpubnames rguenth at gcc dot gnu.org
  2021-03-16 11:59 ` rguenth at gcc dot gnu.org
@ 2021-03-16 21:14 ` mark at gcc dot gnu.org
  2 siblings, 0 replies; 3+ messages in thread
From: mark at gcc dot gnu.org @ 2021-03-16 21:14 UTC (permalink / raw)
  To: gcc-bugs

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

Mark Wielaard <mark at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at gcc dot gnu.org

--- Comment #11 from Mark Wielaard <mark at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #10)
> Mark, you're looking after -gsplit-dwarf - can you comment on whether we can
> drop the -gpubnames "requirement"?

We discussed this a bit on irc. The only reason for the pubnames seems to be
that gold can generate .gdb_index from it. Although it isn't clear if this
usage is common. gdb itself doesn't seem to use pubnames.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-03-16 21:14 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-92442-4@http.gcc.gnu.org/bugzilla/>
2021-03-16 11:54 ` [Bug debug/92442] Compiling Boost.Spirit.X3 code uses exuberant amount of RAM with -gpubnames rguenth at gcc dot gnu.org
2021-03-16 11:59 ` rguenth at gcc dot gnu.org
2021-03-16 21:14 ` mark at gcc dot gnu.org

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).