From: Pedro Alves <pedro@palves.net>
To: gcc-patches@gcc.gnu.org
Cc: gdb-patches@sourceware.org
Subject: [PATCH 0/1] dg-extract-results.{sh, py}: Optionally read file list from stdin/file
Date: Thu, 3 Sep 2026 19:55:27 +0100 [thread overview]
Message-ID: <20260903185528.2542431-1-pedro@palves.net> (raw)
This patch is for the benefit of GDB, but as the binutils-gdb
repository shares the contrib/ directory with GCC, it must first be
applied to GCC and then copied back to binutils-gdb.
On Windows, GDB's "make check-parallel" dies when combining the
per-test gdb.sum / gdb.log files into the final combined pair:
$ find outputs/ -name gdb.sum | wc -l
2657
.../dg-extract-results.sh: line 39: /ucrt64/bin/python3: Argument list too long
make: *** [Makefile:274: check-parallel] Error 2
The GDB testsuite Makefile passes the whole file list to
contrib/dg-extract-results.sh on the command line, expanded from a
find(1) backtick. As GDB's parallel harness writes one gdb.sum (and
one gdb.log) per test script, on a full run that command line argument
list holds thousands of paths, which overflows the Windows
command-line length limit (~32 KB).
This patch teaches dg-extract-results to read the file list from stdin
(or a file) instead. After this is merged, GDB's Makefile will be
changed to pipe the find output straight in, so the length limit no
longer applies regardless of the host.
The GDB patch making use of this is here, if you're curious:
https://inbox.sourceware.org/gdb-patches/20260723175131.266112-5-pedro@palves.net/
Pedro Alves (1):
dg-extract-results.{sh,py}: Optionally read file list from stdin/file
contrib/dg-extract-results.py | 30 ++++++++++++++++++++++++++----
contrib/dg-extract-results.sh | 17 +++++++++++++++--
2 files changed, 41 insertions(+), 6 deletions(-)
base-commit: b3474d5cddda183dcd8d8a2745fba02578816055
--
2.54.0
next reply other threads:[~2026-09-03 18:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 18:55 Pedro Alves [this message]
2026-09-03 18:55 ` [PATCH 1/1] " Pedro Alves
2026-09-04 3:08 ` Andrea Pinski
2026-09-04 12:18 ` Pedro Alves
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=20260903185528.2542431-1-pedro@palves.net \
--to=pedro@palves.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@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