X/Y是正确的…和" >> "移位运算符..如果我们想要二除一个整数，我们可以使用(/)被除数运算符。移位运算符用于移位位。

x = x / 2; x / = 2;我们可以这样用…

我同意其他答案，你应该支持x / 2，因为它的意图更清楚，编译器应该为你优化它。

然而，选择x / 2而不是x >> 1的另一个原因是，如果x是一个有符号int并且是负的，那么>>的行为是依赖于实现的。

ISO C99标准第6.5.7节第5项:

E1 >> E2的结果是E1位右移E2位位置。如果E1 无符号类型，或者E1有符号类型且值为非负值， 结果值为E1 /商的积分部分 2 e2。如果E1具有符号类型和负值，则结果值为 是由实现定义的。

Knuth说:

过早的优化是万恶之源。

所以我建议用x /= 2;

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

X = X / 2;是合适的代码使用..但是一个操作取决于你自己的程序，你想要产生怎样的输出。

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

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).

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

只是加了一个注释

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