From: Jakub Jelinek <email@example.com>
To: Hannes Domani <firstname.lastname@example.org>
Cc: Allan Sandfeld Jensen <email@example.com>,
Mark Wielaard <firstname.lastname@example.org>,
Subject: Re: DWZ 0.14 released
Date: Tue, 9 Mar 2021 12:45:13 +0100 [thread overview]
Message-ID: <20210309114513.GM745611@tucnak> (raw)
On Tue, Mar 09, 2021 at 11:38:07AM +0000, Hannes Domani via Dwz wrote:
> Am Dienstag, 9. März 2021, 10:10:47 MEZ hat Mark Wielaard <email@example.com> Folgendes geschrieben:
> > Hi Allan,
> > On Tue, Mar 09, 2021 at 09:06:54AM +0100, Allan Sandfeld Jensen wrote:
> > > Btw, question for gcc/binutils
> > >
> > > Any reason the work done by tools like dwz couldn't be done in the compiler or
> > > linker? Seems a bit odd to have a post-linker that optimizes the generated
> > > code, when optimizations should already be enabled.
> > dwz does two kinds of optimization. First it attempts to optimize the
> > DWARF debugging information for a given object (executable or shared
> > library). Secondly it tries to put shared pieces of a list of given
> > objects into a supplemental file that gets referenced from all the
> > given object files.
> > Technically the first optimization could be done by the linker. But
> > the second optimization is really a post-linker step.
> Related question: If it were part of binutils, maybe it could be adapted to
> optimize DWARF debugging information of PE files as well.
dwz intentionally uses libelf, it often deals with very large amounts of
debug info that only barely fit into the address space limitations on
certain arches or physical memory for good performance, and any kind of
abstraction penalty (e.g. bfd) would make it slower and more memory hungry.
So no, PE support is not possible.
next prev parent reply other threads:[~2021-03-09 11:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 12:43 Tom de Vries
2021-03-09 8:06 ` Allan Sandfeld Jensen
2021-03-09 9:09 ` Mark Wielaard
2021-03-09 11:38 ` Hannes Domani
2021-03-09 11:45 ` Jakub Jelinek [this message]
2021-03-12 16:48 ` Nick Alcock
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).