> On 26 Nov 2024, at 13:45, Boris Kolpackov <boris_at_[hidden]> wrote:
>
> Iain Sandoe via SG15 <sg15_at_[hidden]> writes:
>
>> AFAIU: the compiler implementers represented (MSVC, clang, GCC) commented
>> that they all have, indeed, have representative mechanisms to do this
>> already (e.g. specifying where ‘/tmp’ is on unix-like systems, and/or
>> specifying the placement of saved intermediate results relative to working
>> directory and/or the object output directory).
>
> Hm, this to me feel very different to what is proposed. What exists is
> the ability to specify the directory for transient files that only exist
> while the compiler is running and are not observable by the build system
> or the user. Or am I missing something here?

I believe what is proposed (in outline, with a paper hopefully to come) is that the place specified would be usable by files that could persist between multiple invocations (and, more contentiously, multiple parallel invocations) of the tools.

Currently, some of the artefacts specified by similar compiler flags are equally intended to be persistent (at least over a build) e.g. dependencies and intermediate files.

Iain