From: mmarek@suse.cz (Michal Marek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] scripts: Add a recorduidiv program
Date: Tue, 1 Dec 2015 17:43:47 +0100 [thread overview]
Message-ID: <565DCE43.7010904@suse.cz> (raw)
In-Reply-To: <20151201161944.GX8644@n2100.arm.linux.org.uk>
On 2015-12-01 17:19, Russell King - ARM Linux wrote:
> On Tue, Dec 01, 2015 at 05:07:05PM +0100, Michal Marek wrote:
>> So, both recordmcount and the new recordudiv program are idempotent.
>> They check if the to-be-added section is already present and do nothing.
>
> They hardly "do nothing", as the (eg) recordmcount plasters the build
> log with warnings. A solution to that would be to make recordmcount
> silent if the section is already present.
Right, there is a warning. The recorduidiv program exits silently.
>> So the result is correct even with CCACHE_HARDLINK, just the
>> intermediate file might be incorrect. If this still is considered an
>> issue, I suggest clearing CCACHE_HARDLINK when using any of these
>> postprocessors, so as not to penalize other use cases.
>
> Another solution would be to have the top level make file unset the
> CCACHE_HARDLINK environment variable if any of the options which enable
> in-place editing of object files is enabled.
This is what I meant, sorry for not being clear.
> Looking at the ccache
> code, the environment variable has to be deleted from the environment
> to turn off the option - and I'm not sure whether make can delete
> environment variables. It certainly can override them, but I see
> nothing in the info pages which suggests that environment variables
> can be deleted by a makefile.
unexport CCACHE_HARDLINK
will do the trick.
Michal
next prev parent reply other threads:[~2015-12-01 16:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 21:51 [PATCH v2 0/2] ARM: Use udiv/sdiv for __aeabi_{u}idiv library functions Stephen Boyd
2015-11-25 21:51 ` [PATCH v2 1/2] scripts: Add a recorduidiv program Stephen Boyd
2015-11-25 23:47 ` Russell King - ARM Linux
2015-11-30 15:11 ` Michal Marek
2015-11-30 15:32 ` Russell King - ARM Linux
2015-11-30 15:40 ` Michal Marek
2015-12-01 16:07 ` Michal Marek
2015-12-01 16:19 ` Russell King - ARM Linux
2015-12-01 16:43 ` Michal Marek [this message]
2015-12-01 16:49 ` Steven Rostedt
2015-12-01 17:10 ` Russell King - ARM Linux
2015-12-01 17:22 ` Steven Rostedt
2015-12-01 18:16 ` Russell King - ARM Linux
2015-12-01 21:39 ` Michal Marek
2015-12-02 10:23 ` Russell King - ARM Linux
2015-12-02 14:05 ` Steven Rostedt
2015-12-11 12:09 ` [PATCH] scripts: recordmcount: break hardlinks Russell King
2015-12-11 14:31 ` Steven Rostedt
2015-12-11 14:45 ` Russell King - ARM Linux
2015-12-11 15:08 ` Steven Rostedt
2015-12-11 18:10 ` Steven Rostedt
2015-12-11 18:33 ` Russell King - ARM Linux
2015-12-11 18:51 ` Steven Rostedt
2015-12-11 18:58 ` Russell King - ARM Linux
2015-12-11 19:28 ` Steven Rostedt
2015-11-25 21:51 ` [PATCH v2 2/2] ARM: Replace calls to __aeabi_{u}idiv with udiv/sdiv instructions Stephen Boyd
2015-11-25 23:09 ` Nicolas Pitre
2015-11-26 0:05 ` Russell King - ARM Linux
2015-11-26 0:07 ` Måns Rullgård
2015-11-26 0:44 ` Nicolas Pitre
2015-11-26 0:50 ` Måns Rullgård
2015-11-26 1:28 ` Russell King - ARM Linux
2015-11-26 2:19 ` Måns Rullgård
2015-11-26 5:32 ` Nicolas Pitre
2015-11-26 12:41 ` Måns Rullgård
2015-11-26 0:08 ` Russell King - ARM Linux
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=565DCE43.7010904@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-arm-kernel@lists.infradead.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 NNTP newsgroup(s).