mirror of
https://gitlab.kitware.com/vtk/vtk-m
synced 2024-10-08 11:29:02 +00:00
1b541bdd37
There were some places in the rendering code where floating point exceptions (FPE) could happen under certain circumstances. Often we do not care about invalid floating point operation in rendering as they often occur in degenerate cases that don't contribute anyway. However, simulations that might include VTK-m might turn on FPE to check their own operations. In such cases, we don't want errant rendering arithmetic causing an exception and bringing down the whole code. Thus, we turn on FPE in some of our test platforms and avoid such operations in general. |
||
|---|---|---|
| .. | ||
| 1.3 | ||
| 1.4 | ||
| 1.5 | ||
| 1.5.1 | ||
| 1.6 | ||
| 1.7 | ||
| 1.7.1 | ||
| 1.8 | ||
| 1.9 | ||
| 2.0 | ||
| 2.1 | ||
| add-slice-multiple-filter.md | ||
| arrayhandle-getcomponents.md | ||
| arrayhandleconstant-extract-component.md | ||
| avoid-rendering-fpe.md | ||
| constant-amr-arrays.md | ||
| intel-union-placeholder.md | ||
| isosurface-uncertainty.md | ||
| new-instance-variable-components.md | ||
| update-warps.md | ||
| users-guide.md | ||
| vecfromportal-operators.md | ||