Nondeterminism in integration test double-read-modf on Windows

[PeterMatula]

Regression test double-read-modf on Windows sometimes fails on:

Test (double-read-modf.c -a pic32 -f elf -c gcc -C -O0 -g)

AssertionError: compilation of file 'regression-tests\integration\current\double-read-modf\outputs\Test (double-read-modf.c -a pic32 -f elf -c gcc -C -O0 -g)\double-read-modf.out.c' failed with return code 1; output:
regression-tests\integration\current\double-read-modf\outputs\Test (double-read-modf.c -a pic32 -f elf -c gcc -C -O0 -g)\double-read-modf.out.c: In function 'func':
regression-tests\integration\current\double-read-modf\outputs\Test (double-read-modf.c -a pic32 -f elf -c gcc -C -O0 -g)\double-read-modf.out.c:27:5: warning: implicit declaration of function 'fpmodf' [-Wimplicit-function-declaration]
     fpmodf((int32_t)x, (int32_t)&intPart);
     ^~~~~~
double-read-modf.out.c:(.text+0x2d): undefined reference to `fpmodf'

Looks like fpmodf() is sometimes generated instead of modff().

[PeterMatula]

Another possible case in integration/strlen/2017-11-14/strlen.x86.gcc.O0.g.exe - run multiple times on the same Linux system.

[s3rvac]

I think the reason is that both modff and fpmodf have the same value (2634040448) and retdec-bin2llvmir fails to compare them in a deterministic way, so sometimes fpmodf is generated instead of modff:

$ retdec-fileinfo double-read-modf.pic32.gcc.O0.g.elf -v | grep 2634040448
1497  modff    DATA OBJECT  GLOBAL   Default visibility   92   2634040448 0
2987  fpmodf   DATA OBJECT  GLOBAL   Default visibility   92   2634040448 0

@PeterMatula, shouldn't this be solved by the changes in #116? IIRC we have discussed this some time ago.