We were mentioning SARIF specifically quite a few times. That is an
interchange format (the IF in SARIF), so it's definitely for users and
their tools to observe. I'm unclear on whether the build system must
observe those, but it's not a bad feature for a build system to create
aggregate SARIF files for all generated SARIF files, at least on request.

On Tue, Nov 26, 2024, 13:44 Boris Kolpackov via SG15 <sg15_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?
> _______________________________________________
> SG15 mailing list
> SG15_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg15
>