search for: absvdi2_test

...alidated patch. A bit of creative grepping yields the following that also look problematic to me: compiler-rt/test/builtins/Unit/absvsi2_test.c: expected = -expected; compiler-rt/test/builtins/Unit/absvti2_test.c: expected = -expected; compiler-rt/test/builtins/Unit/absvdi2_test.c: expected = -expected; I confess I don't fully understand the way these tests are written. E.g. compiler-rt/test/builtins/Unit/absvsi2_test.c: int test__absvsi2(si_int a) { si_int x = __absvsi2(a); si_int expected = a; if (expected < 0)...

Hi, I recently came across the following in __floatsidf in compiler-rt: __floatsidf(int a) { ... if (a < 0) { ... a = -a; In the case where a == INT_MIN, is this negation not undefined behaviour? AIUI this function is used for software emulation on targets that have no hardware floating point support. Perhaps there is an in-built assumption