https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117890
--- Comment #8 from Hu Lin <lin1.hu at intel dot com> --- (In reply to Tamar Christina from comment #7) > (In reply to Hu Lin from comment #5) > > Seems that commit (d2f9159cfe7ea904e6476cabefea0c6ac9532e29) fixed this > > issue. The wrong pattern is no longer generated, although I don't understand > > why for the moment. > > > Are you sure it's not g:51291ad0f1f89a81de917110af96e019dcd5690c that fixed > it? > > That would make more sense. > > The code doesn't have a vector comparison there. so it feels more like > PR117140 > I tried the case at r15-4463-g51291ad0f1f89a, the issue still exists. At least for now, the issue doesn't exist, and I can't re-trigger it. So I want to wait until a similar problem arises, or I can reappear it.
