probinson added a comment. In https://reviews.llvm.org/D52296#1282589, @dblaikie wrote:
> In https://reviews.llvm.org/D52296#1282587, @probinson wrote: > > > Any distributed build has to make this work, so the paths in the line table > > are usable. Not clear what you're thinking might be the problem with the > > split-in-.o case. > > > Fair point - same sort of problem, but might need distinct handling (ie: > might not work "for free" with existing tools, but need more support), etc, > depending on how it's solved? > > Mostly just wondering whether Clang would need extra flags to support this - > to get a sense of the total/overall solution/surface area of the feature, etc. Shouldn't. We have licensees using distributed builds all day every day, but we haven't introduced anything into the compiler itself to make that work. On Windows, I know SN-DBS will intercept system calls to patch up filespecs. On Linux I'd expect the remote servers to set up chroot environments so the path names will Just Work, although I admit I've never actually looked. Never had to; it Just Works. In this patch, where the .o normally points to the .dwo it would instead just point to itself, right? The linker doesn't need to fix anything up, it just ignores the .dwo sections. https://reviews.llvm.org/D52296 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
