From: "H.J. Lu" <hjl.tools@gmail.com>
To: libc-alpha@sourceware.org
Subject: [PATCH 0/2] Update Makefile fragments for DSO sorting tests
Date: Sun, 7 Nov 2021 07:07:25 -0800 [thread overview]
Message-ID: <20211107150727.157003-1-hjl.tools@gmail.com> (raw)
One problem of using
$(objpfx)%$o: $(objpfx)%.c $(before-compile); $$(compile-command.c)
compile-command.c = $(compile.c) $(OUTPUT_OPTION) $(compile-mkdep-flags)
compile.c = $(CC) $< -c $(CFLAGS) $(CPPFLAGS)
to build DSO sorting tests is that $< may not be the source file with
3 "make -j 28" parallel builds on a machine with 112 cores. When
generating Makefile fragments at build time, the same file may be
generated more than once at the same time with parallel builds.
1. Update dso-ordering-test.py to put all sources for DSO sorting tests
in a single directory, dso-sort-tests-src, and compile tests with
"$(compile.c) $(OUTPUT_OPTION)".
2. Generate Makefile fragments for DSO sorting tests at configure time
to avoid generate them in the elf directory during build.
H.J. Lu (2):
dso-ordering-test.py: Put all sources in one directory [BZ #28550]
elf: Pre-generate Makefile fragments for DSO sorting tests [BZ #28550]
configure | 11 +++++++++
configure.ac | 12 +++++++++
elf/Makefile | 22 ++++-------------
scripts/dso-ordering-test.py | 47 ++++++++++++++++++++++++++----------
4 files changed, 62 insertions(+), 30 deletions(-)
--
2.33.1
next reply other threads:[~2021-11-07 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 15:07 H.J. Lu [this message]
2021-11-07 15:07 ` [PATCH 1/2] dso-ordering-test.py: Put all sources in one directory [BZ #28550] H.J. Lu
2021-11-08 13:46 ` Florian Weimer
2021-11-08 14:07 ` H.J. Lu
2021-11-07 15:07 ` [PATCH 2/2] elf: Pre-generate Makefile fragments for DSO sorting tests " H.J. Lu
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=20211107150727.157003-1-hjl.tools@gmail.com \
--to=hjl.tools@gmail.com \
--cc=libc-alpha@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).