> Don't need three different modules, right? A package will either want or > not want x86_64 specific optimizations. Why would a package need to say > "I want this optimization but not the other ones"?
I'd prefer to keep them as separate files if you're okay with it. I did a quick experiment and by wrapping each function in push_options and pop_options pragmas it was pretty easy to get it all working in the same file so I can confirm that option does work. It makes sense to keep them in the same module though, I agree. Ultimately we can delay this decision until we have the avx2/avx512 implementations, I'll rename the module to crc-x86_64 in the meantime though.