FunC gives different results for operator ~%

[jeshecdom]

In the following code:

int calc(int x) {
    return ((x ~% -3) <= 0);
}

int calc3(int x, int y, int z) {
    return ((x ~% y) <= z);
}

calling calc(1) produces -1 (meaning true). But calling calc3(1,-3,0) produces 0 (meaning false).

Expected behavior

It was expected that calc(1) = calc3(1,-3,0), since calc is just a specialization of calc3.

[jeshecdom]

The same happens with comparison operators: <=>, !=, and ==. The following expressions also produce differing results:

• ((x ~% -3) <=> 1) in calc function, and ((x ~% y) <=> z) in cal3 function. We have calc(1) = -1, and calc3(1,-3,1) = 0.
• ((x ~% -3) != 1) in calc function, and ((x ~% y) != z) in cal3 function. We have calc(1) = -1, and calc3(1,-3,1) = 0.
• ((x ~% -3) == 1) in calc function, and ((x ~% y) == z) in cal3 function. We have calc(1) = 0, and calc3(1,-3,1) = -1.