public inbox for debugedit@sourceware.org
 help / color / mirror / Atom feed
From: Kalev Lember <klember@redhat.com>
To: debugedit@sourceware.org
Cc: Kalev Lember <klember@redhat.com>
Subject: [PATCH] find-debuginfo: Pass -j down to dwz
Date: Thu, 19 Jan 2023 17:03:18 +0100	[thread overview]
Message-ID: <20230119160318.3868439-1-klember@redhat.com> (raw)

Now that dwz 0.15 supports parallel jobs, add a way to control it from
here. find-debuginfo already has a -j parameter so we can just extend it
and pass the value down to dwz as well.

This should fix building large packages on memory constrained builders,
such as webkitgtk on s390x in Fedora koji build system, where we can now
use the -j option to tune down parallelism to avoid running out of
memory during dwz run.

Signed-off-by: Kalev Lember <klember@redhat.com>
---
 scripts/find-debuginfo.in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/find-debuginfo.in b/scripts/find-debuginfo.in
index b07a52f..8cc1bfd 100755
--- a/scripts/find-debuginfo.in
+++ b/scripts/find-debuginfo.in
@@ -585,7 +585,7 @@ if $run_dwz \
       dwz_multifile_suffix=".${dwz_multifile_idx}"
     done
     dwz_multifile_name="${dwz_multifile_name}${dwz_multifile_suffix}"
-    dwz_opts="-h -q -r"
+    dwz_opts="-h -q -r -j ${n_jobs}"
     [ ${#dwz_files[@]} -gt 1 ] && [ "$dwz_single_file_mode" = "false" ] \
       && dwz_opts="${dwz_opts} -m .dwz/${dwz_multifile_name}"
     mkdir -p "${RPM_BUILD_ROOT}/usr/lib/debug/.dwz"
-- 
2.39.0


             reply	other threads:[~2023-01-19 16:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 16:03 Kalev Lember [this message]
2023-01-20  8:39 ` Panu Matilainen
2023-01-20 10:27   ` Kalev Lember
2023-01-20 11:27     ` Panu Matilainen
2023-01-26 14:34 ` Mark Wielaard
2023-01-26 15:57   ` Kalev Lember
2023-01-26 23:14     ` Mark Wielaard
2023-01-27 17:37       ` Mark Wielaard
2023-01-28  1:07         ` Kalev Lember

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=20230119160318.3868439-1-klember@redhat.com \
    --to=klember@redhat.com \
    --cc=debugedit@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).