Re: [COMMITTED 4/4] - Implement pointer_or_operator.

2024-10-28 Thread Mikael Morin
Le 28/10/2024 à 14:38, Andrew MacLeod a écrit : On 10/26/24 15:08, Mikael Morin wrote: Hello, Le 24/10/2024 à 14:53, Andrew MacLeod a écrit : diff --git a/gcc/range-op-ptr.cc b/gcc/range-op-ptr.cc index dd312a80366..ef2b2cce516 100644 --- a/gcc/range-op-ptr.cc +++ b/gcc/range-op-ptr.cc (...)

Re: [COMMITTED 4/4] - Implement pointer_or_operator.

2024-10-28 Thread Andrew MacLeod
On 10/26/24 15:08, Mikael Morin wrote: Hello, Le 24/10/2024 à 14:53, Andrew MacLeod a écrit : diff --git a/gcc/range-op-ptr.cc b/gcc/range-op-ptr.cc index dd312a80366..ef2b2cce516 100644 --- a/gcc/range-op-ptr.cc +++ b/gcc/range-op-ptr.cc (...) -void -pointer_or_operator::wi_fold (irange &r

Re: [COMMITTED 4/4] - Implement pointer_or_operator.

2024-10-26 Thread Mikael Morin
Hello, Le 24/10/2024 à 14:53, Andrew MacLeod a écrit : diff --git a/gcc/range-op-ptr.cc b/gcc/range-op-ptr.cc index dd312a80366..ef2b2cce516 100644 --- a/gcc/range-op-ptr.cc +++ b/gcc/range-op-ptr.cc (...) -void -pointer_or_operator::wi_fold (irange &r, tree type, -

[COMMITTED 4/4] - Implement pointer_or_operator.

2024-10-24 Thread Andrew MacLeod
Well, perhaps the subject isn't precise  The existing pointer_or_operator is, like a few others, using irange operands, so is non-functional and this patch removes it. The functionality was never moved to the new dispatch system when Prange was implemented, and IIRC it was because Aldy never f