From: Jakub Jelinek <jakub@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Jason Merrill <jason@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] C++ API database
Date: Tue, 18 Oct 2022 13:15:33 +0200 [thread overview]
Message-ID: <Y06K1ZvDDfx1A6WP@tucnak> (raw)
In-Reply-To: <CAP3s5k-q_Cu6pcv=ESELaHrd3XSmUNiqHgWwZjY3ZCn1gUsfMw@mail.gmail.com>
On Tue, Oct 18, 2022 at 01:01:14PM +0200, Ulrich Drepper via Gcc-patches wrote:
> This is of course not a new problem in general. GNU make has for a long
> time support for order-only prerequisites. With those one can exactly
> express what is needed:
>
> ifeq ($(ENABLE_MAINTAINER_RULES), true)
> FOO.h: FOO.gperf
> else
> FOO.h: | FOO.gperf
> endif
> gperf ...
>
> ifeq ($(ENABLE_MAINTAINER_RULES), true)
> FOO.gperf: CSV
> else
> FOO.gperf: | CSV
> endif
> python ...
>
> The question here is whether there is a reason not to depend on GNU make
> features (and whatever other make implemented this extension).
GCC requires GNU make and we already use order-only prerequisities in
gcc/Makefile.in :
# In order for parallel make to really start compiling the expensive
# objects from $(OBJS) as early as possible, build all their
# prerequisites strictly before all objects.
$(ALL_HOST_OBJS) : | $(generated_files)
Jakub
prev parent reply other threads:[~2022-10-18 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 11:51 Ulrich Drepper
2022-09-28 16:59 ` Ulrich Drepper
2022-10-18 0:56 ` Jason Merrill
2022-10-18 11:01 ` Ulrich Drepper
2022-10-18 11:04 ` Martin Liška
2022-10-18 11:15 ` Jakub Jelinek [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=Y06K1ZvDDfx1A6WP@tucnak \
--to=jakub@redhat.com \
--cc=drepper@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
/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).