From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/25024] dwz: Multifile temporary files too large
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <bug-25024-11298-8VIlSV6ncm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25024-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25024
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
--- Comment #9 from Tom de Vries <vries at gcc dot gnu.org> ---
There are a few things to mention here:
- there is no clear reason why this should be an error, we could also warn
about not being able to add to the temporary files, and continue the
multifile optimization
- it should be possible to continue writing at the point we run into an error
now, by switching to 64-bit dwarf, but reading 64-bit dwarf is currently not
supported.
- the setup of collecting all the info for the multifile optimization into
one temporary file per section is very convenient because it follows the way
single-file optimization is done closely. But things don't have to be setup
like that. We could also have one temporary file per section per input file,
which would fix the limitation we're running into here. Of course we'd
spent more effort juggling things around once we start reading in those
files,
but there is also the possibility that we'd be able to manage memory in
a more fine-grained way, which could possibly reduce peak memory usage.
For now, I'm classifying this as enhancement, given that we're running into an
implementation-defined limitation, which dwz is correctly reporting.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-11-28 12:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 [Bug default/25024] New: " jan.kratochvil at redhat dot com
2019-01-01 0:00 ` [Bug default/25024] " vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org [this message]
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` jan.kratochvil at redhat dot com
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` jan.kratochvil at redhat dot com
2019-01-01 0:00 ` jan.kratochvil at redhat dot com
2019-01-01 0:00 ` jan.kratochvil at redhat dot com
2019-01-01 0:00 ` vries 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-25024-11298-8VIlSV6ncm@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=dwz@sourceware.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).