[Users] Test case requiring strict floating point operation ordering

[David Radice]

Hello Ian,

> The test case test_local_interp_2 in LocalInterp2 is only supposed to pass if the compiler generates code strictly conforming to the ordering dictated by the parentheses in the source code.

> 1. Force the compiler to use strict ordering on that section of the code or that file (I don't know how to do this)
> 2. Disable the test when strict ordering is not available
> 3. Remove the test entirely
> 4. Allow the test to fail on machines whose optionlists do not respect IEEE semantics
> 
> in decreasing order of my own preference.

Users that have applications relying on symmetric interpolation to work property would probably prefer this test to fail unless strict ordering has been preserved by the compiler (and no bugs have been introduced in the relevant code) than having the code silently produce wrong results while in production. So I would recommend against removing it. In any case, users that do not need to have symmetric interpolation would probably prefer to use the AEILocalInterp or the LocalInterp thorns and remove the *LocalInterp2 thorns from their thornlist.

Best,
David
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://lists.einsteintoolkit.org/pipermail/users/attachments/20150512/9f135c7e/attachment.bin