Re: On the subject of module consumer diagnostics.

On 9/6/24 9:41 AM, Ben Boeckel wrote: On Fri, Sep 06, 2024 at 09:30:26 -0400, David Malcolm wrote: On Fri, 2024-09-06 at 08:44 -0400, Ben Boeckel via Gcc wrote: Does this have (additional) implications for caching tools and modules? They cache diagnostic output, but if these other paths showing

Re: On the subject of module consumer diagnostics.

On Fri, Sep 06, 2024 at 09:30:26 -0400, David Malcolm wrote: > On Fri, 2024-09-06 at 08:44 -0400, Ben Boeckel via Gcc wrote: > > Does this have (additional) implications for caching tools and > > modules? > > They cache diagnostic output, but if these other paths showing up or > > disappearing affe

Re: On the subject of module consumer diagnostics.

On Fri, 2024-09-06 at 08:44 -0400, Ben Boeckel via Gcc wrote: > On Tue, Sep 03, 2024 at 16:53:43 +0100, Iain Sandoe wrote: > > I think that might be a misunderstanding on the part of the author; > > AFAIU both GCC and MSVC _do_ require access to the sources at BMI > > consume-time to give decent di

Re: On the subject of module consumer diagnostics.

On Tue, Sep 03, 2024 at 16:53:43 +0100, Iain Sandoe wrote: > I think that might be a misunderstanding on the part of the author; > AFAIU both GCC and MSVC _do_ require access to the sources at BMI > consume-time to give decent diagnostics. I think that there might be > confusion because the compi

Re: On the subject of module consumer diagnostics.

On 9/3/24 11:53 AM, Iain Sandoe wrote: On 3 Sep 2024, at 16:08, Jason Merrill via Gcc wrote: On 9/3/24 7:30 AM, Jonathan Wakely wrote: On Tue, 3 Sept 2024, 10:15 Iain Sandoe, mailto:i...@sandoe.co.uk>> wrote: Hi Folks, When we build a C++ binary module (CMI/BMI), we obviously have

Re: On the subject of module consumer diagnostics.

> On 3 Sep 2024, at 16:08, Jason Merrill via Gcc wrote: > > On 9/3/24 7:30 AM, Jonathan Wakely wrote: >> On Tue, 3 Sept 2024, 10:15 Iain Sandoe, > > wrote: >>Hi Folks, >>When we build a C++ binary module (CMI/BMI), we obviously have >>access to its source

Re: On the subject of module consumer diagnostics.

On Tue, 3 Sept 2024 at 12:30, Jonathan Wakely wrote: > > > > On Tue, 3 Sept 2024, 10:15 Iain Sandoe, wrote: >> >> 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

Re: On the subject of module consumer diagnostics.

On 9/3/24 7:30 AM, Jonathan Wakely wrote: On Tue, 3 Sept 2024, 10:15 Iain Sandoe, > wrote: 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 mod

Re: On the subject of module consumer diagnostics.

On Tue, Sep 03, 2024 at 03:30:05PM +0100, Iain Sandoe wrote: > > > > On 3 Sep 2024, at 13:59, Nathaniel Shead wrote: > > > > On Tue, Sep 03, 2024 at 10:14:29AM +0100, Iain Sandoe wrote: > >> Hi Folks, > >> > >> When we build a C++ binary module (CMI/BMI), we obviously have access to > >> its

Re: On the subject of module consumer diagnostics.

> On 3 Sep 2024, at 13:59, Nathaniel Shead wrote: > > On Tue, Sep 03, 2024 at 10:14:29AM +0100, Iain Sandoe wrote: >> 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

Re: On the subject of module consumer diagnostics.

On Tue, Sep 03, 2024 at 10:14:29AM +0100, Iain Sandoe wrote: > 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

Re: On the subject of module consumer diagnostics.

On Tue, 3 Sept 2024, 10:15 Iain Sandoe, wrote: > 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 diagn