[libc-dev] __builtin_* vs llvm-libc provided ones?

Ebrahim Byagowi via libc-dev libc-dev at lists.llvm.org
Sat Jan 30 10:00:57 PST 2021

There is e.g. __builtin_memcpy and even a __builtin_memcpy_inline in clang,
and __builtin_memset_inline
is just a TODO right now.

As __builtin_memcpy for example already has an implementation on llvm
but llvm-libc hasn't reused it and implemented it separately, maybe perhaps
in order to not make llvm-libc a clang buildable only project as maybe some
builtins aren't present in other compilers.

My question is what is the plan about the two, accepting the duplication of
implementations or removing non libc implementation in favor of llvm libc
provided ones or the reverse way.

I wonder if is there a future that all or most of the libc entries will
also be provided by compiler's __builtin_* and maybe __builin_*_inline also
thus resolving the TODO __builin_memset_inline by just reusing llvm-libc
implementations somehow on IRBuilder.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/libc-dev/attachments/20210130/2cd6e985/attachment.html>

More information about the libc-dev mailing list