Re: value-range.cc:2165: ICE in invert

On Tue, Sep 3, 2024 at 6:12 PM Andrew MacLeod wrote: > > > On 8/25/24 03:48, Richard Biener wrote: > > On Sat, Aug 24, 2024 at 6:19 PM Georg-Johann Lay wrote: > >> Trying to use the value-range interface and functions I am running > >> into that ICE when using invert(). > >> > >> From what the

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: v2.2 Draft for an elementsof paper

On Wed, 14 Aug 2024 23:10:17 +0200 Alejandro Colomar via Gcc wrote: > - Rename lengthof => elementsof. Aaron found incompatible existing >functions called lengthof() in the wild. Hi Alejandro, I have a suggestion and an open-ended question. The suggestion: Instead of elementsof, name

Re: value-range.cc:2165: ICE in invert

On 8/25/24 03:48, Richard Biener wrote: On Sat, Aug 24, 2024 at 6:19 PM Georg-Johann Lay wrote: Trying to use the value-range interface and functions I am running into that ICE when using invert(). From what the sources suggest, invert() computes the complement of the current set (the unio

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

On the subject of module consumer diagnostics.

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 sou