On Tuesday, 5 November 2013 at 16:31:23 UTC, bearophile wrote:
Don:
A compiler intrinsic, which generates no code (simply
inserting a barrier for the optimiser) sounds like the correct
approach.
Coming up for a name for this operation is difficult.
Something like this?
noFPOpt
naiveFP
literalFP
asisFP
FPbarrier
barrierFP
The name should be about the semantic, not the intended behavior
(optimization barrier). My ideas:
x + precisely!float(y - z)
x + exactly!float(y - z)
x + exact!float(y - z)
x + strictly!float(y - z)
x + strict!float(y - z)
x + strictfp!float(y - z) // familiar for Java programmers
