Date: Mon, 10 Mar 2025 09:40:40 -0700
On Monday, 10 March 2025 02:20:14 Pacific Daylight Time Sebastian Wittmeier via
Std-Proposals wrote:
> In practice, it would be the job of the build system, not of the compiler to
> decide to recompile.
>
>
> It probably would not be compatible with any build cache.
It would be compatible with (s)ccache, because those store the preprocessed
output, if the feature is implemented by parsing a preprocessor macro like I
suggested in another email. That would mean the output is cached, but it would
always be a cache-miss on recompilation because the time keeps changing.
The alternative is that it is an intrinsic without preprocessor changes, in
which case the output would be cached and it would hit on reuse. That in turn
means you will keep getting the time of the first cache, until you clean the
cache or the output expires from the cache.
Std-Proposals wrote:
> In practice, it would be the job of the build system, not of the compiler to
> decide to recompile.
>
>
> It probably would not be compatible with any build cache.
It would be compatible with (s)ccache, because those store the preprocessed
output, if the feature is implemented by parsing a preprocessor macro like I
suggested in another email. That would mean the output is cached, but it would
always be a cache-miss on recompilation because the time keeps changing.
The alternative is that it is an intrinsic without preprocessor changes, in
which case the output would be cached and it would hit on reuse. That in turn
means you will keep getting the time of the first cache, until you clean the
cache or the output expires from the cache.
-- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Principal Engineer - Intel DCAI Platform & System Engineering
Received on 2025-03-10 16:40:42