You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When compiled with the Intel compilers (version 18.0.3 20180410, JasPer version 2.0.22), the ternary operation at lines 1393-1395 returns a floating invalid when cp->totalsize == UINT_FAST32_MAX. Replacing the ternary operation with the if-else block located on lines 1397-1401 returns the expected value of UINT_FAST32_MAX.
The text was updated successfully, but these errors were encountered:
What's the compiler define macro for that intel compilers?
On the other hand I don't get why we wouldn't want the more readable expression on the latter lines in all cases. I'll create a PR for this and let @mdadams review it.
jubalh
added a commit
to jubalh/jasper
that referenced
this issue
Jan 18, 2021
If this ternary operation creates a problem on some clang version.
Why not just use the more readable if clause in all cases?
jasper-software#260 further reports
that it also creates problems on intel compilers.
Instead of adding more and more checks for compatible compilers let's
just use the if clause.
Fixesjasper-software#260
When compiled with the Intel compilers (version 18.0.3 20180410, JasPer version 2.0.22), the ternary operation at lines 1393-1395 returns a floating invalid when
cp->totalsize == UINT_FAST32_MAX
. Replacing the ternary operation with the if-else block located on lines 1397-1401 returns the expected value ofUINT_FAST32_MAX
.The text was updated successfully, but these errors were encountered: