-
Notifications
You must be signed in to change notification settings - Fork 5
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
CPU does not seem to support SSE2 #3
Comments
$ gcc -dumpmachine
x86_64-linux-gnu $ gcc --version
gcc (Debian 8.3.0-6) 8.3.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ gcc -march=native -dM -E - </dev/null | grep SSE2
#define __SSE2_MATH__ 1
#define __SSE2__ 1 EDIT1: Added go version: $ go version
go version go1.11.6 linux/amd64 EDIT2: Tested using earlier version of go, still same issue:
References:
|
@mooijtech @alcore did anybody figure this one out? I am having the same issue; however, if I simply run tests in sno's repository, everything works fine. |
I figured it out -- 1.1.0 does not contain fixes required for this to work. @alcore any chance you can release a new tagged version? |
Apologies! This somehow ended up under my radar and I had a large hiatus -- correct, a tag push didn't make it upstream. https://github.com/muyo/sno/tree/v1.2.0 is now tagged and released. I'll leave this open for a while should anything else have slipped by my attention. |
Solution: upgrade to 1.2.0 Following the discussion in muyo/sno#3, @alcore released 1.2.0
Hello,
Thank you for this awesome library, I appreciate it a lot.
I intend to use it for generating IDs related to PST email messages (importing to ClickHouse).
I am getting the following panic on my Linux local machine and VPS:
As you can see "flags" contains "sse2" which the library is complaining about.
I was wondering if you have any solution to this?
Thanks in advance,
Marten
The text was updated successfully, but these errors were encountered: