On Tue, Jan 14, 2025 at 2:35 PM Richard Biener wrote:
>
> On Tue, 14 Jan 2025, Christoph Müllner wrote:
>
> > On Tue, Jan 14, 2025 at 1:46 PM Richard Biener wrote:
> > >
> > > On Tue, 14 Jan 2025, Christoph Müllner wrote:
> > >
> > > > As reported in PR117079, commit ab18785840d7b8 broke the test
On Tue, 14 Jan 2025, Christoph Müllner wrote:
> On Tue, Jan 14, 2025 at 1:46 PM Richard Biener wrote:
> >
> > On Tue, 14 Jan 2025, Christoph Müllner wrote:
> >
> > > As reported in PR117079, commit ab18785840d7b8 broke the test pr105493.c.
> > > When looking at the generated code, we can see that
On Tue, Jan 14, 2025 at 1:46 PM Richard Biener wrote:
>
> On Tue, 14 Jan 2025, Christoph Müllner wrote:
>
> > As reported in PR117079, commit ab18785840d7b8 broke the test pr105493.c.
> > When looking at the generated code, we can see that the generated code
> > is vectorized differently, resultin
On Tue, 14 Jan 2025, Christoph Müllner wrote:
> As reported in PR117079, commit ab18785840d7b8 broke the test pr105493.c.
> When looking at the generated code, we can see that the generated code
> is vectorized differently, resulting in a reduction from 225 instructions
> down to 109. On the perfo
As reported in PR117079, commit ab18785840d7b8 broke the test pr105493.c.
When looking at the generated code, we can see that the generated code
is vectorized differently, resulting in a reduction from 225 instructions
down to 109. On the performance side, no changes were measured on a 5950X.
This
