On 12/12/22 13:05, Martin Liška wrote:
> On 12/12/22 12:42, Jakub Jelinek wrote:
>> On Mon, Dec 12, 2022 at 12:39:36PM +0100, Martin Liška wrote:
I'm fine with backporting the whole
series to GCC 12 but I wonder if earlier still maintained versions are also
affected (noting that the
On 12/12/22 12:42, Jakub Jelinek wrote:
> On Mon, Dec 12, 2022 at 12:39:36PM +0100, Martin Liška wrote:
>>> I'm fine with backporting the whole
>>> series to GCC 12 but I wonder if earlier still maintained versions are also
>>> affected (noting that the series also addresses WPA streaming which is
On Mon, Dec 12, 2022 at 12:39:36PM +0100, Martin Liška wrote:
> > I'm fine with backporting the whole
> > series to GCC 12 but I wonder if earlier still maintained versions are also
> > affected (noting that the series also addresses WPA streaming which is
> > not part of the "troubles" here).
>
>
On 12/11/22 11:47, Richard Biener wrote:
> On Fri, Dec 9, 2022 at 11:07 AM Martin Liška wrote:
>>
>> Hi.
>>
>> As make 4.4 has been release, it switches to FIFO by default. That makes
>> troubles to the latest GCC release, version 12.
>
> Can you elaborate on "troubles" here?
Sure. Problem with
On Fri, Dec 9, 2022 at 11:07 AM Martin Liška wrote:
>
> Hi.
>
> As make 4.4 has been release, it switches to FIFO by default. That makes
> troubles to the latest GCC release, version 12.
Can you elaborate on "troubles" here? I'm fine with backporting the whole
series to GCC 12 but I wonder if ea
On Fri, 2022-12-09 at 11:07 +0100, Martin Liška wrote:
> Hi.
>
> As make 4.4 has been release, it switches to FIFO by default. That makes
> troubles to the latest GCC release, version 12. Right now, we've been using
> the following 4 patches in openSUSE gcc12 package:
>
> 1270ccda70ca09f7d4fe76b5
