diff options
| author | Guillaume Chatelet <gchatelet@google.com> | 2023-02-06 13:03:18 +0000 |
|---|---|---|
| committer | Guillaume Chatelet <gchatelet@google.com> | 2023-02-07 09:32:34 +0000 |
| commit | 83e98c85564aca127094e34d44d21ce7f7e95fbb (patch) | |
| tree | a5510525335a6f1c02466b72abfa266c7c0af2b4 /libc/docs | |
| parent | 8a09d60b71c0f9cac25834553c9eafb1e9bd58d6 (diff) | |
| download | llvm-83e98c85564aca127094e34d44d21ce7f7e95fbb.tar.gz | |
[libc][doc] Update compiler
Differential Revision: https://reviews.llvm.org/D143389
Diffstat (limited to 'libc/docs')
| -rw-r--r-- | libc/docs/compiler_support.rst | 11 |
1 files changed, 9 insertions, 2 deletions
diff --git a/libc/docs/compiler_support.rst b/libc/docs/compiler_support.rst index a139cd93c8d2..cc671126451b 100644 --- a/libc/docs/compiler_support.rst +++ b/libc/docs/compiler_support.rst @@ -4,14 +4,21 @@ Compiler Support ================ -As of now only ``Clang`` is fully supported. +``LLVM libc`` compiles from both ``Clang`` and ``GCC`` but for maximum +performance we recommand using ``Clang``. -We are in the process of supporting ``GCC`` but some memory function implementations rely on `compiler intrinsics`__ that are not currently available in ``GCC``. +Indeed, some memory function implementations rely on `compiler intrinsics`__ +that are not currently available in ``GCC``. As such we cannot guarantee optimal performance for these functions. .. __: https://clang.llvm.org/docs/LanguageExtensions.html#guaranteed-inlined-copy +For platforms where only ``GCC`` is natively available but maximum performance +is required it is possible to bootstrap ``Clang`` with ``GCC`` and then use +``Clang`` to build the '`libc``" project. + Minimum version =============== - ``Clang 11`` + - ``GCC 12.2``` |