[libc-commits] [PATCH] D151822: [libc][docs] Update implementation status tables for Memory and String Functions.

[Siva Chandra via Phabricator via libc-commits]

sivachandra added a comment.

In general, I think just listing every target architecture for every function is not scalable. I think we should separate platform independent implementations from platform specific implementations. The platform independent implementations are straightforward to list. We can include the tables only for platform specific implementations. For items like the optimized memory functions, I think we can say something like this:

  Platform independent, tiny, byte-by-byte implementations of `memcpy`, ... are available for size sensitive embedded and bare-metal platforms. For performance sensitive use cases, optimized flavors for x86_64, aarch64 and riscv64 are also available.



================
Comment at: libc/docs/strings.rst:56
+
+  - `barebone-aarch32 <https://github.com/llvm/llvm-project/tree/main/libc/config/baremetal/arm/entrypoints.txt>`_ 
+
----------------
What is barebone-aarch32?


================
Comment at: libc/docs/strings.rst:69
+|            +---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+
+|            | x86_64  | aarch64 | aarch32 | riscv64 | x86_64  | aarch64 | x86_64  | aarch64 | aarch32 | riscv32 | AMD     | nVidia  |
++============+=========+=========+=========+=========+=========+=========+=========+=========+=========+=========+=========+=========+
----------------
Should this be aarch32 or the more popular term Arm32?


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D151822/new/

https://reviews.llvm.org/D151822