From: Carlos O'Donell <carlos@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH v2] benchtests: Generate .d dependency files [BZ #28922]
Date: Fri, 25 Feb 2022 10:39:52 -0500 [thread overview]
Message-ID: <0a7db2b8-7eb8-be3d-3e45-fb02a8344cb3@redhat.com> (raw)
In-Reply-To: <20220224221035.987093-1-hjl.tools@gmail.com>
On 2/24/22 17:10, H.J. Lu via Libc-alpha wrote:
> 1. Add all .o files to extra-objs.
> 2. Include ../Rules after extra-objs has been set.
LGTM. Fixes the ../Rules part. Still looks good.
Reviewed-by: Carlos O'Donell <carlos@redhat.com>
> ---
> benchtests/Makefile | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/benchtests/Makefile b/benchtests/Makefile
> index 9b8df3b3f5..d513b29903 100644
> --- a/benchtests/Makefile
> +++ b/benchtests/Makefile
> @@ -296,11 +296,12 @@ bench-extra-objs = json-lib.o
> extra-objs += $(bench-extra-objs)
> others-extras = $(bench-extra-objs)
>
> -include ../Rules
> -
> binaries-bench := $(addprefix $(objpfx)bench-,$(bench))
> +extra-objs += $(addsuffix .o,$(addprefix bench-,$(bench)))
> binaries-benchset := $(addprefix $(objpfx)bench-,$(benchset))
> +extra-objs += $(addsuffix .o,$(addprefix bench-,$(benchset)))
> binaries-bench-malloc := $(addprefix $(objpfx)bench-,$(bench-malloc))
> +extra-objs += $(addsuffix .o,$(addprefix bench-,$(bench-malloc)))
>
> # The default duration: 1 seconds.
> ifndef BENCH_DURATION
> @@ -334,6 +335,9 @@ run-bench = $(test-wrapper-env) \
> $($*-ENV) $(test-via-rtld-prefix) $${run}
>
> timing-type := $(objpfx)bench-timing-type
> +extra-objs += bench-timing-type.o
> +
> +include ../Rules
>
> # This makes sure CPPFLAGS-nonlib and CFLAGS-nonlib are passed
> # for all these modules.
--
Cheers,
Carlos.
prev parent reply other threads:[~2022-02-25 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 22:10 H.J. Lu
2022-02-25 15:39 ` Carlos O'Donell [this message]
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=0a7db2b8-7eb8-be3d-3e45-fb02a8344cb3@redhat.com \
--to=carlos@redhat.com \
--cc=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).