| 1 |
On Mon, Feb 25, 2013 at 5:34 PM, Diego Elio Pettenò |
| 2 |
<flameeyes@×××××××××.eu> wrote: |
| 3 |
> No, an example of _how building a whole package with -ffast-math_ was |
| 4 |
> brought up, and you turned it into "something that it should apply to" |
| 5 |
> (which is false, and stupid to say). |
| 6 |
|
| 7 |
Perhaps this is part of the issue then. I didn't not read that email |
| 8 |
and get the impression that the whole package was being built against |
| 9 |
that flag. If it ever worked I'd be quite impressed (and it would |
| 10 |
likely be because the build system ignored it most of the time |
| 11 |
anyway). |
| 12 |
|
| 13 |
If that really was the example, then I can understand why my |
| 14 |
referencing it suggested that I supported this kind of use of the |
| 15 |
flag. |
| 16 |
|
| 17 |
> Software does not work like a single equation. Ever heard of fuzzing? |
| 18 |
> You know why it works? Because a single different bit can have cascade |
| 19 |
> effects. |
| 20 |
|
| 21 |
Hadn't really thought of it that way, but it makes sense. Propagation |
| 22 |
of error applies to random error when applied to integrable functions. |
| 23 |
That breaks down as soon as you stick an if() in your code. But hey, |
| 24 |
fractals are pretty... |
| 25 |
|
| 26 |
Rich |
Archives