Re: [PATCH] i386: Fix pr101950-2.c [PR115028]

2025-02-25 Thread Andrew Pinski
On Tue, Feb 25, 2025 at 1:05 AM Jakub Jelinek wrote: > > On Thu, Feb 20, 2025 at 01:11:25PM -0800, Andrew Pinski wrote: > > So what is happening here is that after r15-268-g9dbff9c05520a7, > > a move instruction still exists after combine and the register > > allocator choses different register al

Re: [PATCH] i386: Fix pr101950-2.c [PR115028]

2025-02-25 Thread Jakub Jelinek
On Thu, Feb 20, 2025 at 01:11:25PM -0800, Andrew Pinski wrote: > So what is happening here is that after r15-268-g9dbff9c05520a7, > a move instruction still exists after combine and the register > allocator choses different register allocation order for the xor > and because the input operand of lz

[PATCH] i386: Fix pr101950-2.c [PR115028]

2025-02-20 Thread Andrew Pinski
So what is happening here is that after r15-268-g9dbff9c05520a7, a move instruction still exists after combine and the register allocator choses different register allocation order for the xor and because the input operand of lzcntq is not the same as output operand, there is an extra xor that happ