第一个看起来像除法吗?不。如果你想除法，用x / 2。如果可能的话，编译器可以优化它使用位移位(它被称为强度减少)，这使得它成为一个无用的微优化，如果你自己做它。

显然，如果你是在为下一个阅读你的代码的人写代码，那么你应该追求“x/2”的清晰度。

然而，如果速度是你的目标，那就两种方法都试一试，把握好时间。几个月前，我做了一个位图卷积例程，它涉及到在一个整数数组中步进，并将每个元素除以2。我做了各种各样的事情来优化它，包括用“x>>1”代替“x/2”的老技巧。

当我计算这两种方式时，我惊奇地发现x/2比x>>1快

这是使用Microsoft VS2008 c++并打开默认优化。

我们有很多理由支持使用x = x / 2;以下是一些例子:

it expresses your intent more clearly (assuming you're not dealing with bit twiddling register bits or something) the compiler will reduce this to a shift operation anyway even if the compiler didn't reduce it and chose a slower operation than the shift, the likelihood that this ends up affecting your program's performance in a measurable way is itself vanishingly small (and if it does affect it measurably, then you have an actual reason to use a shift) if the division is going to be part of a larger expression, you're more likely to get the precedence right if you use the division operator: x = x / 2 + 5; x = x >> 1 + 5; // not the same as above signed arithmetic might complicate things even more than the precedence problem mentioned above to reiterate - the compiler will already do this for you anyway. In fact, it'll convert division by a constant to a series of shifts, adds, and multiplies for all sorts of numbers, not just powers of two. See this question for links to even more information about this.

简而言之，当你真正想要进行乘法或除法运算时，编写移位代码并没有什么好处，除了可能会增加引入错误的可能性。自从编译器不够聪明到在适当的时候优化这类事情到移位以来，已经过去了。

Mod 2, test for = 1。不知道c中的语法，但这可能是最快的。

这个问题的答案取决于你工作的环境。

If you're working on an 8-bit microcontroller or anything without hardware support for multiplication, bit shifting is expected and commonplace, and while the compiler will almost certainly turn x /= 2 into x >>= 1, the presence of a division symbol will raise more eyebrows in that environment than using a shift to effect a division. If you're working in a performance-critical environment or section of code, or your code could be compiled with compiler optimization off, x >>= 1 with a comment explaining its reasoning is probably best just for clarity of purpose. If you're not under one of the above conditions, make your code more readable by simply using x /= 2. Better to save the next programmer who happens to look at your code the 10 second double-take on your shift operation than to needlessly prove you knew the shift was more efficient sans compiler optimization.

所有这些假设都是无符号整数。简单的移位可能不是你想要的符号。此外，DanielH提出了一个关于在ActionScript等特定语言中使用x *= 0.5的好观点。

x / 2更清晰，x >> 1快不了多少(根据一个微基准测试，对于Java JVM快30%左右)。正如其他人所注意到的，对于负数，舍入略有不同，所以当您想处理负数时必须考虑这一点。一些编译器可能会自动将x / 2转换为x >> 1，如果他们知道这个数字不可能是负数(即使我无法验证这一点)。

即使x / 2可能不使用(慢)除法CPU指令，因为一些捷径是可能的，但它仍然比x >> 1慢。

(This is a C / C++ question, other programming languages have more operators. For Java there is also the unsigned right shift, x >>> 1, which is again different. It allows to correctly calculate the mean (average) value of two values, so that (a + b) >>> 1 will return the mean value even for very large values of a and b. This is required for example for binary search if the array indices can get very large. There was a bug in many versions of binary search, because they used (a + b) / 2 to calculate the average. This doesn't work correctly. The correct solution is to use (a + b) >>> 1 instead.)