search for: __builtin_abs

On 2/18/2013 8:08 PM, Chris Lattner wrote: > > That code is presumably compiled by someone. If whoever compiles it specifies -fno-builtin, the attribute would be added to it. It doesn't affect its clients. I thought that no-builtin attached to foo means that foo should not be considered a builtin function. For example, if someone wrote their own printf, they may want to mark it as

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

...clares standard library functions after including their headers. The inline keyword is intended only to provide users with a portable way to suggest inlining of functions. Because the standard headers need not be portable, implementations have other options along the lines of: #define abs(x) __builtin_abs(x) or other non-portable mechanisms for inlining standard library functions. -------------- next part -------------- >From GCC 2.95.3 Manual ====================== 4.31 An Inline Function is As Fast As a Macro By declaring a function inline, you can direct GNU CC to integrate that function...