From: Ingo Molnar <mingo@kernel.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-kbuild@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
x86@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH v2,10/10] kbuild: mark $(targets) as .SECONDARY and remove .PRECIOUS markers
Date: Tue, 27 Mar 2018 08:09:11 +0200 [thread overview]
Message-ID: <20180327060911.iljk66zfuqnl472e@gmail.com> (raw)
In-Reply-To: <1522079634-5947-1-git-send-email-yamada.masahiro@socionext.com>
* Masahiro Yamada <yamada.masahiro@socionext.com> wrote:
> GNU Make automatically deletes intermediate files that are updated
> in a chain of pattern rules.
>
> Example 1) %.dtb.o <- %.dtb.S <- %.dtb <- %.dts
> Example 2) %.o <- %.c <- %.c_shipped
>
> A couple of makefiles mark such targets as .PRECIOUS to prevent Make
> from deleting them, but the correct way is to use .SECONDARY.
>
> .SECONDARY
> Prerequisites of this special target are treated as intermediate
> files but are never automatically deleted.
>
> .PRECIOUS
> When make is interrupted during execution, it may delete the target
> file it is updating if the file was modified since make started.
> If you mark the file as precious, make will never delete the file
> if interrupted.
>
> Both can avoid deletion of intermediate files, but the difference is
> the behavior when Make is interrupted; .SECONDARY deletes the target,
> but .PRECIOUS does not.
>
> The use of .PRECIOUS is relatively rare since we do not want to keep
> partially constructed (possibly corrupted) targets.
>
> Another difference is that .PRECIOUS works with pattern rules whereas
> .SECONDARY does not.
>
> .PRECIOUS: $(obj)/%.lex.c
>
> works, but
>
> .SECONDARY: $(obj)/%.lex.c
>
> has no effect. However, for the reason above, I do not want to use
> .PRECIOUS which could cause obscure build breakage.
>
> The targets specified as .SECONDARY must be explicit. $(targets)
> contains all targets that need to include .*.cmd files. So, the
> intermediates you want to keep are mostly in there. Therefore, mark
> $(targets) as .SECONDARY. It means primary targets are also marked
> as .SECONDARY, but I do not see any drawback for this.
>
> I replaced some .SECONDARY / .PRECIOUS markers with 'targets'. This
> will make Kbuild search for non-existing .*.cmd files, but this is
> not a noticeable performance issue.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> Acked-by: Frank Rowand <frowand.list@gmail.com>
> ---
> arch/arc/boot/dts/Makefile | 2 --
> arch/arm/crypto/Makefile | 2 +-
> arch/arm64/crypto/Makefile | 2 +-
> arch/metag/boot/dts/Makefile | 2 --
> arch/sparc/vdso/Makefile | 4 +---
> arch/x86/entry/vdso/Makefile | 4 +---
Acked-by: Ingo Molnar <mingo@kernel.org>
Thanks,
Ingo
prev parent reply other threads:[~2018-03-27 6:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 15:53 Masahiro Yamada
2018-03-27 6:09 ` Ingo Molnar [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=20180327060911.iljk66zfuqnl472e@gmail.com \
--to=mingo@kernel.org \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=sparclinux@vger.kernel.org \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.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
all inboxes | Powered by JetHome®