search for: __xxx_acos

...These solve a related but different - CodeGen - problem. RTLIB libcalls are used when we're not able to select some IR instruction/intrinsic so have to rely on a runtime library helper function (e.g., the stuff in compiler-rt/lib/builtins/). So, #1 and #2 would make LLVM able to emit calls to __xxx_acos when it sees "@llvm.acos.f32", but it won't let LLVM optimize (constant fold, transform into the intrinsic, ...) "__xx_acos()" when it sees it. It sounds like you also want to recognize and optimize these calls. That involves (pre-CodeGen) IR-level optimizations. No, I don&...

Tim, Are you referring to setLibcallName? That is target specific yes but there isn't RTLIB for most of the libm functions, for example, for acos this doesn't apply. Ideally what I would like is to create a libc with functions like acos called something like __xxx_acos that can still be recognized to be optimized. RTLIB is pretty limited but it works fine, I can just use setLibcallName(RTLIB::floor, "__xxx_floor")... but again, the functions that are RTLIB are limited. Using intrinsics make it more difficult because then you have to match the intrinsi...

...o select some IR >> >> >> instruction/intrinsic so have to rely on a runtime library helper >> >> >> function (e.g., the stuff in compiler-rt/lib/builtins/). >> >> >> >> >> >> So, #1 and #2 would make LLVM able to emit calls to __xxx_acos when >> >> >> it sees "@llvm.acos.f32", but it won't let LLVM optimize (constant >> >> >> fold, transform into the intrinsic, ...) "__xx_acos()" when it sees >> >> >> it. >> >> >> >> >> >&...

In the first code I see a 'tail call @acos', in the second code I see a tail call @llvm.acos.f32'. (sorry, there should be only one input for acos, I've been trying many libm/libc functions). Not sure why it's called TargetLibraryInfo if it's not in target specific code? It seems that ALL targets use this code, making it generic. Am I missing something here? Basically