https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117890
--- Comment #6 from Tamar Christina <tnfchris at gcc dot gnu.org> --- (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. The commit was a correctness fix on vector comparisons. My guess is that the ~ was done before on the wrong precision. You'd have to look at the scalar code after pattern matching in the vectorizer. But it's not unexpected that commit would fix it, since it was aimed and correcting vector boolean comparisons for early break :)
