Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid SSE3 and SSSE3 dependency #46

Closed
torognes opened this issue Feb 16, 2015 · 3 comments
Closed

Avoid SSE3 and SSSE3 dependency #46

torognes opened this issue Feb 16, 2015 · 3 comments
Assignees
Labels

Comments

@torognes
Copy link
Owner

The Swarm code is compiled with "-mssse3" in the Makefile. A few ssse3 instructions are used in the alignment code if present, otherwise the code is written to only require sse2, and the presence of sse2 is tested for. However, it seems that the compiler also uses some sse3 or ssse3 instructions somewhere. This results in termination of Swarm with "Illegal instruction" fatal errors on some architectures that does not support all sse3 or ssse3 instructions. Two reports from users indicate this (both using pick_denovo_otus.py in qiime).

The code should be recompiled with other compiler options in the Makefile to avoid this problem.

@torognes torognes added the bug label Feb 16, 2015
@torognes torognes self-assigned this Feb 16, 2015
@colinbrislawn
Copy link

Qiime is configured to uses swarm 1.2.19 followed by swarm_breaker.py. If qiime users are reporting this, the problem may be replicable in an older version of swarm.

@frederic-mahe
Copy link
Collaborator

I've tested the new version 1.2.21 and it works correctly on my computer (clustering results are unchanged). I've tried to compare the behavior of versions 1.2.20 and 1.2.21 on the oldest cluster nodes I could find (PowerEdge M605 Blade Server from 2009, AMD Opteron), but they both behave similarly, without any error messages. The next step is to ask the QIIME maintainers to point to a new release of swarm to see if it solves the SSE3 dependency problem reported by a few users.

@torognes
Copy link
Owner Author

torognes commented Mar 6, 2015

We assume this is solved in version 1.2.21.

@torognes torognes closed this as completed Mar 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants