Update SSE code to use esl_sse_{left,right}shiftz_float

[althonos]

Hi !

There were some places in the code where _m128 vectors were being left/right shifted with an external zerov null vector, which was causing an unneeded move compared to using the esl_sse_*shiftz_float function.

In locations where a leftshift was done by a _mm_move_ss followed by a _mm_shuffle_ps, it makes it a bit clearer what's happening.

[npcarter]

Martin, Thanks for this work, it looks like good stuff. GitHub has a bit of an issue with your pull request, in that it can't find a branch to base it off of. Because of that, I've copied your changes into our develop branch by hand, and am most of the way through testing them. Assuming they pass, I'm going to reject the pull request on GitHub to take it off of our pending list, but the changes you've made will go into our next release. By the way, do you know when you'll be finishing your Ph.D., and have you thought about what you'll do next? We hope to have an opening for a programmer on the HMMER effort opening up fairly soon, assuming the funding is approved.

…

-Nick

On Mon, Jun 7, 2021 at 6:17 AM Martin Larralde ***@***.***> wrote: Hi ! There were some places in the code where _m128 vectors were being left/right shifted with an external zerov null vector, which was causing an unneeded move compared to using the esl_sse_*shiftz_float function. In locations where a leftshift was done by a _mm_move_ss followed by a _mm_shuffle_ps, it makes it a bit clearer what's happening. ------------------------------ You can view, comment on, or merge this pull request online at: #242 Commit Summary - Update `impl_sse/fwdback.c` to use `esl_sse_leftshiftz_float` where applicable - Use `esl_sse_rightshiftz_float` instead of `esl_sse_rightshift_ps` when in shifting zeros File Changes - *M* src/impl_sse/fwdback.c <https://github.com/EddyRivasLab/hmmer/pull/242/files#diff-fbd072e551fcceebb11a01661fe164e4739127079cb44dc49a67125514adff97> (61) - *M* src/impl_sse/optacc.c <https://github.com/EddyRivasLab/hmmer/pull/242/files#diff-5591e7c7c998069c3c3d13d02d85a40ef38e2f566c9688a164d11575bad96796> (144) - *M* src/impl_sse/stotrace.c <https://github.com/EddyRivasLab/hmmer/pull/242/files#diff-2b28485bfd89556b4ea46b36921e650728963c040dd6d03eb3921af6b6a94ad8> (72) Patch Links: - https://github.com/EddyRivasLab/hmmer/pull/242.patch - https://github.com/EddyRivasLab/hmmer/pull/242.diff — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#242>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDJBZHIZQ27S6XO2J2GR63TRSMDZANCNFSM46HK3KLA> .

[npcarter]

I've finished testing these changes, and they pass all my tests. To make GitHub happier, I've copied them into our develop branch manually and have committed those changes. I'm going to close this pull request since the changes were added manually rather than by accepting the pull. Thanks, Martin!

[althonos]

Hi Nick, no problem! Thanks for testing it, and glad the code works as expected.

By the way, do you know when you'll be finishing your Ph.D., and have you thought about what you'll do next? We hope to have an opening for a programmer on the HMMER effort opening up fairly soon, assuming the funding is approved.

I still have two more years to go, but thanks for the heads-up! Scientific programming is definitely a direction I would like to explore, more than data science like I'm doing right now 😉

[npcarter]

Thanks for the reply. Good luck with the degree!

…

-Nick

On Wed, Jun 9, 2021 at 2:53 PM Martin Larralde ***@***.***> wrote: Hi Nick, no problem! Thanks for testing it, and glad the code works as expected. By the way, do you know when you'll be finishing your Ph.D., and have you thought about what you'll do next? We hope to have an opening for a programmer on the HMMER effort opening up fairly soon, assuming the funding is approved. I still have two more years to go, but thanks for the heads-up! Scientific programming is definitely a direction I would like to explore, more than data science like I'm doing right now 😉 — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#242 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDJBZF3KUHG7TETHQTAQFDTR62EHANCNFSM46HK3KLA> .