回复：0.3.8 中的比特币新币生成功能坏了吗？
原始发布页
打开来源页面查看 1 个交叉存档
我发现 SSE2 只带来了轻微的 2% 速度提升，似乎不值得为此引入不兼容。我当时想选择更安全的做法。
在我看来，Crypto++ 似乎不可能在运行时决定是否使用 SSE2。有一处会检测 SSE2，以便决定某个区块计数参数，但 SSE2 相关内容在编译时全都由 #ifdef 控制，我看不出它如何能在运行时切换。也许是我没找对地方。
我们是否应该在所有 makefile 中启用 SSE2？看来必须这样做，以防有人用 64 位方式编译。
我会重新编译 Linux 0.3.8 发行版的 64 位部分。
英文原文
展开英文原文
I found that SSE2 only added a slight 2% speedup, which didn't seem worth the incompatibility. I was trying to take the safer option.
It doesn't look to me like Crypto++ could be deciding whether to use SSE2 at runtime. There's one place where it detects SSE2 for deciding some block count parameter, but the SSE2 stuff is all #ifdef at compile time and I can't see how that would switch at runtime. Maybe I'm not looking in the right place.
Should we enable SSE2 in all the makefiles? It seems like we must in case someone compiles with 64-bit.
I will recompile the 64-bit part of the Linux 0.3.8 release.