dwblaikie wrote: I think at least with Bazel we use `-fdebug-compilation-dir=/proc/cwd` to create build-path-agnostic builds. Is that something you folks can use, rather than adding this new option? Or is there some other way we could make `-fdebug-compilation-dir` address this? (like differentiate between empty and non-present? (so `-fdebug-compilation-dir=` would do what you want (awkward, in that it redefines the behavior that someone might be relying on) and then maybe some flag value for "go back to the default" like `-fdebug-compilation-dir=<default>` or the like) - there was also some attempt by Chrome folks to propose an explicit representation of relative path in comp_dir, but ended up I think as https://dwarfstd.org/issues/210628.1.html (the historic links seem to be dead, unfortunately))
https://github.com/llvm/llvm-project/pull/149897 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
