vvereschaka wrote:

Thanks @cachemeifyoucan ,

> From the test case, I see this is for implicit module build? Can you 
> elaborate on what the use case for this is?
> 
> What I see is this is trying to make pcm/pch not encode some local file paths 
> by moving the local file path onto command-line options? I don't think it is 
> a reproducible build problem so I assume you want to do some distributed 
> build support? This can make two different builds from different paths to 
> produce the same output using different compiler command-lines, but it also 
> made it impossible diagnose if there is a prefix mapping problem when seeing 
> a missing file/dependency error.

There is a quite big overlapped chunk of that is required for the reproducible 
builds and the distributed builds. We are focused on the reproducible builds 
here, i.e. building of the same source code exactly the same way side by side 
but only the root directory is different.

Yes, diagnostics is getting worse, but looks like this is an expectable 
situation for any similar cases with the path prefix manipulations.

https://github.com/llvm/llvm-project/pull/203662
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to