Lines Matching +full:ninja +full:- +full:build

21 depending on the build configuration. The GPU target is considered a full build
22 and therefore provides all of its own utilities to build and run the generated
25 #. **Hermetic tests** - These are unit tests built with a test suite similar to
27    tests except that the entire environment is self-hosted. This allows us to
31 #. **Integration tests** - These are lightweight tests that simply call a
32    ``main`` function and checks if it returns non-zero. These are primarily used
47 --------------
57 .. code-block:: c++
76 --------------
80 kernels on the given device. Currently we provide the ``amdhsa-loader`` and
81 ``nvptx-loader`` targeting the AMD HSA runtime and CUDA driver runtime
84 .. code-block:: sh
86    $> clang++ crt1.o test.cpp --target=amdgcn-amd-amdhsa -mcpu=native -flto
87    $> amdhsa_loader --threads 1 --blocks 1 ./a.out
92 of threads and blocks to be set can be controlled with ``--threads`` and
93 ``--blocks``. These also accept additional ``x``, ``y``, ``z`` variants for
105 #. **Cross build** - If the C library was built using ``LLVM_ENABLE_PROJECTS``
106    or a runtimes cross build, then the standard targets will be present in the
107    base CMake build directory.
109    #. All tests - You can run all supported tests with the command:
111       .. code-block:: sh
113         $> ninja check-libc
115    #. Hermetic tests - You can run hermetic with tests the command:
117       .. code-block:: sh
119         $> ninja libc-hermetic-tests
121    #. Integration tests - You can run integration tests by the command:
123       .. code-block:: sh
125         $> ninja libc-integration-tests
127 #. **Runtimes build** - If the library was built using ``LLVM_ENABLE_RUNTIMES``
128    then the actual ``libc`` build will be in a separate directory.
130    #. All tests - You can run all supported tests with the command:
132       .. code-block:: sh
134         $> ninja check-libc-amdgcn-amd-amdhsa
135         $> ninja check-libc-nvptx64-nvidia-cuda
137    #. Specific tests - You can use the same targets as above by entering the
138       runtimes build directory.
140       .. code-block:: sh
142         $> ninja -C runtimes/runtimes-amdgcn-amd-amdhsa-bins check-libc
143         $> ninja -C runtimes/runtimes-nvptx64-nvidia-cuda-bins check-libc
144         $> cd runtimes/runtimes-amdgcn-amd-amdhsa-bins && ninja check-libc
145         $> cd runtimes/runtimes-nvptx64-nvidia-cuda-bins && ninja check-libc