probinson added a comment. In https://reviews.llvm.org/D44788#1046093, @dblaikie wrote:
> In implicit ThinLTO, the object files are only temporary. > > Sort of similar to using -gsplit-dwarf when compiling straight to an > executable (without using -c): "clang++ x.cpp y.cpp -o a.out" - where > should the .dwo files go then? If they go where the .o files go, then > they'll be in /tmp/ and get deleted either when the ocmpiler ends after it > runs the linker, or perhaps at some uncertain point in the future when the > temp space is reclaimed. I think that the .dwo files generally go where the user-specified final output goes. So in your example they would go where a.out goes, not where the intermediate/temporary .o files go. Being able to override that is fine, but being required to specify a directory in order to get fission in the first place is not. Repository: rC Clang https://reviews.llvm.org/D44788 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
