From: Chung-Lin Tang <chunglin_tang@mentor.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: GNU C Library <libc-alpha@sourceware.org>,
Carlos O'Donell <carlos@redhat.com>, <cltang@codesourcery.com>,
Catherine Moore <clm@codesourcery.com>
Subject: Re: [PATCH v2 1/2] BZ #17645, fix slow DSO sorting behavior in dynamic loader
Date: Tue, 19 May 2020 22:33:02 +0800 [thread overview]
Message-ID: <e467b3a0-446d-d87e-5115-bf57ebb775a8@mentor.com> (raw)
In-Reply-To: <87a724uhtf.fsf@igel.home>
On 2020/5/19 10:21 PM, Andreas Schwab wrote:
> On Mai 19 2020, Chung-Lin Tang wrote:
>
>> +define include_dsosort_tests
>> +# We use the existence of the Makefile fragment file to indicate if we need to
>> +# regenerate all sources and script for this test file.
>> +$(shell if ! test -f "$(objpfx)$(1).tmp-makefile"; then \
>> + $(PYTHON) $(..)scripts/dso-ordering-test.py --description-file $(1) \
>> + --objpfx $(objpfx) --output-makefile $(objpfx)$(1).tmp-makefile; fi)
>> +include $(objpfx)$(1).tmp-makefile
>> +endef
>
> You can just write a rule that creates $(objpfx)$(1).tmp-makefile, no
> need to use $(shell).
Do you mean that an include target is automatically re-made?
Thanks,
Chung-Lin
>> +# Currently all tests are defined in description files, and this function is
>> +# not utilized, but kept here for possible conveniences.
>> +define single_dsosort_test
>> +$(shell $(PYTHON) $(..)scripts/dso-ordering-test.py --objpfx $(objpfx) \
>> + $(2) $(1) $(3) --output-makefile $(objpfx)$(1).tmp-makefile)
>> +include $(objpfx)$(1).tmp-makefile
>> +endef
>
> Likewise.
>
> Andreas.
>
next prev parent reply other threads:[~2020-05-19 14:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 13:24 Chung-Lin Tang
2020-05-19 14:21 ` Andreas Schwab
2020-05-19 14:33 ` Chung-Lin Tang [this message]
2020-05-19 14:50 ` Andreas Schwab
2020-05-20 14:38 ` [PATCH v2.1 " Chung-Lin Tang
2020-06-05 13:56 ` Carlos O'Donell
2020-06-18 21:30 ` Carlos O'Donell
2020-07-22 18:10 ` [PATCH v3 " Chung-Lin Tang
2020-07-27 0:40 ` Carlos O'Donell
2020-07-27 10:00 ` Chung-Lin Tang
2020-07-27 10:12 ` Florian Weimer
2020-08-08 4:42 ` Carlos O'Donell
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=e467b3a0-446d-d87e-5115-bf57ebb775a8@mentor.com \
--to=chunglin_tang@mentor.com \
--cc=carlos@redhat.com \
--cc=clm@codesourcery.com \
--cc=cltang@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.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).