| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
Mauri de Souza MeneguzzoI spotted some possible problems with your PR:
1. You usually need to reference a bug number for all but trivial or cosmetic fixes. For this repo, the format is usually 'Fixes #12345' or 'Updates #12345' at the end of the commit message. Should you have a bug reference?Please address any problems by updating the GitHub PR.
When complete, mark this comment as 'Done' and click the [blue 'Reply' button](https://go.dev/wiki/GerritBot#i-left-a-reply-to-a-comment-in-gerrit-but-no-one-but-me-can-see-it) above. These findings are based on heuristics; if a finding does not apply, briefly reply here saying so.
To update the commit title or commit message body shown here in Gerrit, you must edit the GitHub PR title and PR description (the first comment) in the GitHub web interface using the 'Edit' button or 'Edit' menu entry there. Note: pushing a new commit to the PR will not automatically update the commit message used by Gerrit.
For more details, see:
- [how to update commit messages](https://go.dev/wiki/GerritBot/#how-does-gerritbot-determine-the-final-commit-message) for PRs imported into Gerrit.
- the Go project's [conventions for commit messages](https://go.dev/doc/contribute#commit_messages) that you should follow.
(In general for Gerrit code reviews, the change author is expected to [log in to Gerrit](https://go-review.googlesource.com/login/) with a Gmail or other Google account and then close out each piece of feedback by marking it as 'Done' if implemented as suggested or otherwise reply to each review comment. See the [Review](https://go.dev/doc/contribute#review) section of the Contributing Guide for details.)
Done
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
VCMEQ V0.D2, V4.D2, V8.D2It seems very strange to use .D2 here instead of .B16. Is there a reason for that?
VAND V8.B16, V11.B16, V8.B16Instead of ((V8&V9)&V10)&V11, do (V8&V9)&(V10&V11).
ADD $8, R0This needs a comment, tricky things are happening.
Part of the confusion is that the entry point `tail` needs a comment. It is not checking [R0:R0+R6] like everywhere else is. It is checking [R0+R6:R0+R6+8].
Previously it was always expecting R6 to be negative. Now here we are coyly not incrementing R0 and passing a positive R6.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
VCMEQ V0.D2, V4.D2, V8.D2It seems very strange to use .D2 here instead of .B16. Is there a reason for that?
Ehh, no good reason. That's just a mistake. .D2 zeroes an entire lane on a mismatch, while .B16 compares all bytes individually. Both happen to work here because the result is eventually reduced with VUMINV.B16, but .B16 is the right choice since we're doing a byte comparison in the first place.
VAND V8.B16, V11.B16, V8.B16Instead of ((V8&V9)&V10)&V11, do (V8&V9)&(V10&V11).
Thanks, didn't see the parallel opportunity there.
ADD $8, R0This needs a comment, tricky things are happening.
Part of the confusion is that the entry point `tail` needs a comment. It is not checking [R0:R0+R6] like everywhere else is. It is checking [R0+R6:R0+R6+8].
Previously it was always expecting R6 to be negative. Now here we are coyly not incrementing R0 and passing a positive R6.
Acknowledged
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |