Replies: 6 comments
-
What about dropping the use of that x86-64-modern arch in any of our CI, releases, wiki examples, etc but just keep it for backwards compatibility (i.e. so the target is available, it may still be commonly referenced)? In that case we can also update it, as it won't matter much. |
Beta Was this translation helpful? Give feedback.
-
I agree with vondele, we should move away from targets with vague and changing meaning completely. |
Beta Was this translation helpful? Give feedback.
-
I'm to drop "x86-64-modern" everywhere, keep a temporary deprecated target to be dropped as well after N month(s). |
Beta Was this translation helpful? Give feedback.
-
I'd vote for renaming it popcnt. |
Beta Was this translation helpful? Give feedback.
-
It currently is an alias for But, my feeling is that most want to stop using / deprecating x86-64-modern as an arch specifier, and explicitly call the thing by its full name. On the download page we'll have to find a way to guide users to the appropriate binary (probably taking into account that most users don't want to be try multiple binaries that crash, btw). |
Beta Was this translation helpful? Give feedback.
-
see #4691 |
Beta Was this translation helpful? Give feedback.
-
Stockfish/src/Makefile
Line 788 in e87e103
AVX2 was released on Intel CPUs 10 years ago and on AMD CPUs 8 years ago.
https://en.wikipedia.org/wiki/Advanced_Vector_Extensions#CPUs_with_AVX2
Intel
AMD
2 votes ·
Beta Was this translation helpful? Give feedback.
All reactions