Michael Ferguson

For example, here's a C program that does this with GCC: ``` c #pragma STDC FENV_ACCESS on #define _GNU_SOURCE #include int main() { #ifdef FE_NOMASK_ENV fesetenv(FE_NOMASK_ENV); #endif double zero =...

> What Inf and NaN are you talking about? Maybe I need to see the code. At which one of the multitude in ../shootout/mandelbrot/ferguson/... should I look please? Why does...

@bradcray - > These recent comments make me wonder whether floating point modes and changes to them (if any) should perhaps be done via methods on locale types (rather than...

@bradcray @damianmoz - I've moved the compile-time assumption part to #11986. @damianmoz - I think we're in general agreement about this but there are some finer points that I tried...

> is that the approach you'd imagined? Not sure exactly what approach we need, but if I were to work on it, the first place I would look is how...

Regarding the previous two comments - yes, I agree that would be a good short-term solution.

Damian, sorry it is giving you trouble. I will try to explain what is happening. > The problem seems to stem from the default typing of integral literals. From what...

> How will I write this number if I want it to occur in a 128-bit floating point expression? Or for that matter, a 256-bit precision expression? The floating-point literal...

Using `--no-remote-value-forwarding` does not change the inconsistency. (Neither does `--fast`, FWIW).

I have a pretty good guess why it's inconsistent. I think it's because the `forall` has two coforalls in the iterator, one for locales, (then the on statement), then a...