From: Tom de Vries <tdevries@suse.de>
To: dwz@sourceware.org, jakub@redhat.com, mark@klomp.org
Subject: [committed] Apply multifile_force_{ptr_size,endian} ASAP
Date: Mon, 29 Mar 2021 10:14:21 +0200 [thread overview]
Message-ID: <20210329081419.GA2225@delia> (raw)
Hi,
Rather than waiting for multi_ptr_size/multi_endian to be set in
write_multifile, apply multifile_force_{ptr_size,endian} ASAP, in
dwz_files_1. This is a preparation for running write_multifile
in parallel.
Committed to trunk.
Thanks,
- Tom
Apply multifile_force_{ptr_size,endian} ASAP
2021-03-29 Tom de Vries <tdevries@suse.de>
* dwz.c (dwz_files_1): Apply multifile_force_ptr_size and
multifile_force_endian.
---
dwz.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/dwz.c b/dwz.c
index 9adc9df..3ad9c9e 100644
--- a/dwz.c
+++ b/dwz.c
@@ -16502,6 +16502,11 @@ dwz_files_1 (int nr_files, char *files[], bool hardlink,
if (multifile)
{
+ if (multifile_force_ptr_size)
+ multi_ptr_size = multifile_force_ptr_size;
+ if (multifile_force_endian)
+ multi_endian = multifile_force_endian;
+
multi_info_fd = make_temp_file ("dwz.debug_info");
multi_abbrev_fd = make_temp_file ("dwz.debug_abbrev");
multi_line_fd = make_temp_file ("dwz.debug_line");
reply other threads:[~2021-03-29 8:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210329081419.GA2225@delia \
--to=tdevries@suse.de \
--cc=dwz@sourceware.org \
--cc=jakub@redhat.com \
--cc=mark@klomp.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).