Lines Matching +full:docs +full:- +full:libc +full:- +full:html

17 `this guide <https://llvm.org/docs/HowToAddABuilder.html>`_ for information
21 `Linux script <https://github.com/llvm/llvm-zorg/blob/main/zorg/buildbot/builders/annotated/libc-linux.py>`_
23 `Windows script <https://github.com/llvm/llvm-zorg/blob/main/zorg/buildbot/builders/annotated/libc-windows.py>`_
29 If you are starting to bring up LLVM's libc on a new operating system, the first
30 step is to add a directory for that OS in the ``libc/config`` directory. Both
31 `Linux <https://github.com/llvm/llvm-project/tree/main/libc/config/linux>`_ and
32 `Windows <https://github.com/llvm/llvm-project/tree/main/libc/config/windows>`_,
33 the two operating systems on which LLVM's libc is being actively developed,
38    `Darwin <https://github.com/llvm/llvm-project/tree/main/libc/config/darwin>`_
41 .. note:: LLVM's libc is being brought up on the
49 There are parts of the libc which are implemented differently for different
51 its internal implementation - its Linux implementation differs for different
52 architectures. Since a large part of the libc makes use of syscalls (or an
53 equivalent on non-Linux like platforms), it might be simpler and convenient to
54 bring up the libc for one architecture at a time. In such cases, wherein the
55 support surface of LLVM's libc differs for each target architecture, one will
60 `x86_64 <https://github.com/llvm/llvm-project/tree/main/libc/config/linux/x86_64>`_
61 and `aarch64 <https://github.com/llvm/llvm-project/tree/main/libc/config/linux/aarch64>`_.
62 The libc CMake machinery looks for subdirectories named after the target
70 :ref:`entrypoints`) you want to include in the static archive of the libc (for
77 architecture separately: `aarch64 <https://github.com/llvm/llvm-project/tree/main/libc/config/linux/aarch64>`_,
78 `arm32 <https://github.com/llvm/llvm-project/tree/main/libc/config/linux/arm>`_ and
79 `x86_64 <https://github.com/llvm/llvm-project/tree/main/libc/config/linux/x86_64>`_. On the
81 `file <https://github.com/llvm/llvm-project/tree/main/libc/config/windows/entrypoints.txt>`_.
86 same is the case if one is implementing a new entrypoint - the target for the
97 provided by the libc. This is relevant only if the libc is to be used in the
102 `aarch64 <https://github.com/llvm/llvm-project/tree/main/libc/config/linux/aarch64>`_
104 `x86_64 <https://github.com/llvm/llvm-project/tree/main/libc/config/linux/x86_64>`_