search for: fsqrtf

...() so for me this is unimportant ... > 2. Codegen fsin/fcos to fsin/fcos for X86. We cannot do this, except > under the control of something like -enable-unsafe-fp-math. These > instructions are architected to have a limited range. OK, I will add this flag. > 3. Codegen fsqrt/fsqrtf C functions to the FSQRT dag node. These > functions can set errno, so this is not a safe transformation. The > proper way to do this is to introduce an llvm.sqrt.f32/llvm.sqrt.f64 > pair of intrinsics to represent these operations without errno. The > optimizer can then...

...We already catch this at the DAG level. If we aren't, please let me know. 2. Codegen fsin/fcos to fsin/fcos for X86. We cannot do this, except under the control of something like -enable-unsafe-fp-math. These instructions are architected to have a limited range. 3. Codegen fsqrt/fsqrtf C functions to the FSQRT dag node. These functions can set errno, so this is not a safe transformation. The proper way to do this is to introduce an llvm.sqrt.f32/llvm.sqrt.f64 pair of intrinsics to represent these operations without errno. The optimizer can then turn fsqrt calls...

Hello, I have been gone for a while, finishing work on my Master's thesis... Now that I'm back I updated LLVM to the most recent version and found that my FP_ABS SelectionDAGNode type and code generation was now conflicting with the new FABS node type. I brought the rest of my local modifications in line with the FABS implementation, so here is my patch that includes sqrt, sin and cos