Displaying 3 results from an estimated 3 matches for "rl291909".
2017 Mar 29
3
clang 4.0.0: Invalid code for builtin floating point function with -mfloat-abi=hard -ffast-math (ARM)
...float-abi` (that is, -mfloat-abi=hard => AAPCS/VFP,
> -mfloat-abi=soft => AAPCS).
Exactly, but they're not, and that's the problem. Do you have any idea
why -ffast-math would change their PCS for libc calls?
The behaviour seems to have been by your patch
(https://reviews.llvm.org/rL291909), so maybe there's some
transformation that uses the run-time functions, or some other badly
coupled logic...
cheers,
--renato
2017 Mar 21
3
clang 4.0.0: Invalid code for builtin floating point function with -mfloat-abi=hard -ffast-math (ARM)
Hello,
clang/llvm 4.0.0 generates invalid calls for builtin functions with
-mfloat-abi=hard -ffast-math.
Small example fail.c:
// clang -O2 -target armv7a-none-none-eabi -mfloat-abi=hard
-ffast-math -S fail.c -o -
extern float sinf (float x);
float sin1 (float x) {return (sinf (x));}
generates code to pass the parameter in r0 and expect the result in r0.
The same code without
2017 Mar 24
2
clang 4.0.0: Invalid code for builtin floating point function with -mfloat-abi=hard -ffast-math (ARM)
On 22 March 2017 at 01:38, Friedman, Eli <efriedma at codeaurora.org> wrote:
>> Small example fail.c:
>>
>> // clang -O2 -target armv7a-none-none-eabi -mfloat-abi=hard -ffast-math
>> -S fail.c -o -
>> extern float sinf (float x);
>> float sin1 (float x) {return (sinf (x));}
I changed your example slightly to make sure we're passing the