Hi Folks, When we build a C++ binary module (CMI/BMI), we obviously have access to its source to produce diagnostics, all fine.
However, when we consume that module we might also need access to the sources used to build it - since diagnostics triggered in the consumer can refer back to the sources used. Currently clang has been experimenting with embedding the sources into the BMI - this can make things seem more efficient when, for example, distributing BMIs to remote nodes in a large-scale distributed build. There was a patch proposed to make this the default for clang, which has resulted in the discussion here: https://discourse.llvm.org/t/rfc-modules-should-we-embed-sources-to-the-bmi/81029 Does GCC have a plan to deal with this? .. if so can we communicate it.. .. if not, then what do we think about this strategy? .. at the very least trying to avoid tooling divergence seems a worthwhile objective. thanks Iain
