Jeff Law writes:
> On 4/2/23 14:06, Andrew Pinski wrote:
>> On Sun, Apr 2, 2023 at 12:55 PM Jeff Law via Gcc-patches
>> wrote:
>>>
>>>
>>>
>>> On 3/31/23 12:44, Sam James wrote:
Kito Cheng writes:
> It's not the RISC-V part, so this requires a global maintainer there I
On Sun, Apr 2, 2023 at 1:07 PM Jeff Law wrote:
>
>
>
> On 4/2/23 14:06, Andrew Pinski wrote:
> > On Sun, Apr 2, 2023 at 12:55 PM Jeff Law via Gcc-patches
> > wrote:
> >>
> >>
> >>
> >> On 3/31/23 12:44, Sam James wrote:
> >>>
> >>> Kito Cheng writes:
> >>>
> It's not the RISC-V part, so
On 4/2/23 14:06, Andrew Pinski wrote:
On Sun, Apr 2, 2023 at 12:55 PM Jeff Law via Gcc-patches
wrote:
On 3/31/23 12:44, Sam James wrote:
Kito Cheng writes:
It's not the RISC-V part, so this requires a global maintainer there I think?
Someone able to look at the system.h bit? It
On Sun, Apr 2, 2023 at 12:55 PM Jeff Law via Gcc-patches
wrote:
>
>
>
> On 3/31/23 12:44, Sam James wrote:
> >
> > Kito Cheng writes:
> >
> >> It's not the RISC-V part, so this requires a global maintainer there I
> >> think?
> >>
> >
> > Someone able to look at the system.h bit? It should be
On 3/31/23 12:44, Sam James wrote:
Kito Cheng writes:
It's not the RISC-V part, so this requires a global maintainer there I think?
Someone able to look at the system.h bit? It should be trivial, there's
no uses left and it was added purely for a bug like this in the past
(see commit
Kito Cheng writes:
> It's not the RISC-V part, so this requires a global maintainer there I think?
>
Someone able to look at the system.h bit? It should be trivial, there's
no uses left and it was added purely for a bug like this in the past
(see commit message).
> On Tue, Mar 14, 2023 at
