Strictfp确保在每个平台上从浮点计算中得到完全相同的结果。如果不使用strictfp, JVM实现可以在可用的地方使用额外的精度。

来自JLS:

Within an FP-strict expression, all intermediate values must be elements of the float value set or the double value set, implying that the results of all FP-strict expressions must be those predicted by IEEE 754 arithmetic on operands represented using single and double formats. Within an expression that is not FP-strict, some leeway is granted for an implementation to use an extended exponent range to represent intermediate results; the net effect, roughly speaking, is that a calculation might produce "the correct answer" in situations where exclusive use of the float value set or double value set might result in overflow or underflow.

换句话说，就是要确保Write-Once-Run-Anywhere实际上意味着write - once - get - equal - wrong - results - everywhere。

使用strictfp，您的结果是可移植的，没有它，它们更可能是准确的。

Strictfp确保在每个平台上从浮点计算中得到完全相同的结果。如果不使用strictfp, JVM实现可以在可用的地方使用额外的精度。

来自JLS:

Within an FP-strict expression, all intermediate values must be elements of the float value set or the double value set, implying that the results of all FP-strict expressions must be those predicted by IEEE 754 arithmetic on operands represented using single and double formats. Within an expression that is not FP-strict, some leeway is granted for an implementation to use an extended exponent range to represent intermediate results; the net effect, roughly speaking, is that a calculation might produce "the correct answer" in situations where exclusive use of the float value set or double value set might result in overflow or underflow.

换句话说，就是要确保Write-Once-Run-Anywhere实际上意味着write - once - get - equal - wrong - results - everywhere。

使用strictfp，您的结果是可移植的，没有它，它们更可能是准确的。

strictfp是一个关键字，可以用作类或方法的非非访问修饰符(但不能用作变量)。将类标记为strictfp意味着类中的任何方法代码都将符合IEEE 754浮点标准规则。

如果没有这个修饰符，方法中使用的浮点可能会以依赖于平台的方式运行。有了它，无论JVM运行在哪个底层平台上，您都可以预测浮点数的行为。缺点是，如果底层平台能够支持更高的精度，那么strictfp方法将无法利用它。

如果您没有将一个类声明为strictfp，那么通过将一个方法声明为strictfp，您仍然可以在逐个方法的基础上获得strictfp行为。

~ SCJP Sun®Java™6认证程序员- Kathy Sierra & Bert Bates ~

'strictfp'关键字用于强制Java中的浮点计算(float或double)的精度显式符合IEEE的754标准。如果不使用strictfp关键字，浮点精度取决于目标平台的硬件。

如果接口或类使用strictfp声明，那么该接口或类中的所有方法和嵌套类型都是隐式strictfp。

参考链接

实际上，维基百科上有一篇关于strictfp的好文章，其中有一个指向Java规范中浮点类型、格式和值部分的链接。

字里行间的意思是，如果您没有指定strictfp，那么JVM和JIT编译器就有权按它们想要的方式计算您的浮点计算。为了提高速度，它们很可能将计算委托给您的处理器。在使用strictfp时，计算必须符合IEEE 754算术标准，这在实践中可能意味着JVM将执行计算。

那么为什么要使用strictfp呢?我能看到的一个场景是在分布式应用程序(或多人游戏)中，无论底层硬件或CPU是什么，所有浮点计算都需要是确定的。代价是什么?很可能是执行时间。

一切都始于一个故事，

When java was being developed by James Gosling, Herbert and rest of his team. They had this crazy thing in mind called platform independency. They wanted to make oak(Java) so much better that it would run exactly same on any machine having different instruction set, even running different operating systems. But, there was a problem with decimal point numbers also known as floating point and double in programming languages. Some machines were built targeting efficiency while rest were targeting accuracy. So, the later(more accurate) machines had size of floating point as 80 bits while the former(more efficient/faster) machines had 64 bit doubles. But, this was against there core idea of building a platform independent language. Also, this might lead to loss of precision/data when a code is built on some machine(having double of 64 bit size) and run on another kind of machine(having double of 80 bit size).

扩大规模是可以容忍的，但缩小规模是不能容忍的。 因此，他们遇到了strictfp的概念，即严格浮点数。如果在类/函数中使用此关键字，则其浮点数和双精度浮点数在任何机器上都具有一致的大小。即分别为32位/64位。