我发现 SSE2 只带来 2% 的轻微提速，似乎不值得为之牺牲兼容性。我选了更保守的方案。
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.
在我看来 Crypto++ 不像是在运行时决定是否用 SSE2。有一处它检测 SSE2 是为了决定某个块数参数，但 SSE2 相关的东西在编译期全是 #ifdef，我看不出它在运行时怎么切换。也许我没找对地方。
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.
我们该在所有 makefile 里启用 SSE2 吗？看起来必须，万一有人用 64 位编译。
Should we enable SSE2 in all the makefiles? It seems like we must in case someone compiles with 64-bit.
我会重编 Linux 0.3.8 发布版的 64 位部分。
I will recompile the 64-bit part of the Linux 0.3.8 release.
当前版本尚未建立逐条校对状态记录。来源核验、历史审校与当前译文校对是不同事项。
译文内容版本：9f8d77219418。用于比对文本，不代表校对等级或更新时间。
请填写对应原文、现译文、建议译法和理由。复制后通过你联系本站作者的渠道提交；此处不会自动发送。
