使用x = x / 2;或x /= 2;因为将来有可能会有一个新的程序员使用它。因此，他更容易发现代码行中发生了什么。每个人可能都不知道这种优化。

只是加了一个注释

在一些基于vm的语言中，x *= 0.5通常会更快——尤其是actionscript，因为变量不需要被检查是否除以0。

我想说有几件事需要考虑。

Bitshift should be faster, as no special computation is really needed to shift the bits, however as pointed out, there are potential issues with negative numbers. If you are ensured to have positive numbers, and are looking for speed then I would recommend bitshift. The division operator is very easy for humans to read. So if you are looking for code readability, you could use this. Note that the field of compiler optimization has come a long way, so making code easy to read and understand is good practice. Depending on the underlying hardware, operations may have different speeds. Amdal's law is to make the common case fast. So you may have hardware that can perform different operations faster than others. For example, multiplying by 0.5 may be faster than dividing by 2. (Granted you may need to take the floor of the multiplication if you wish to enforce integer division).

如果您追求的是纯粹的性能，我建议您创建一些可以执行数百万次操作的测试。对执行进行多次采样(您的样本量)，以确定哪一个在统计上最适合您的操作系统/硬件/编译器/代码。

使用最能描述您要做的事情的操作。

如果你将数字作为一个比特序列来处理，请使用bitshift。 如果你把它当作一个数值，使用除法。

请注意，它们并不完全相等。对于负整数，它们可以给出不同的结果。例如:

-5 / 2  = -2
-5 >> 1 = -3

(ideone)

Knuth说:

过早的优化是万恶之源。

所以我建议用x /= 2;

这样代码很容易理解，而且我认为这种形式的操作优化，对处理器来说不会有太大的区别。

在性能方面。CPU的移位运算比除法运算快得多。 所以除以2或乘以2等都可以从移位运算中获益。

至于外观和感觉。作为工程师，我们什么时候变得如此依赖化妆品，连漂亮的女士都不用!：）