Lines Matching +full:clang +full:- +full:15

5 - bundle: copies the sources and the `build.py` file into
7 - build: builds the actual go binary, assuming it is executed
12 build from there without a dependency on toolchain-utils
21 (chroot) ~/trunk/src/third_party/toolchain-utils/compiler_wrapper/install_compiler_wrapper.sh
30 into chromiumos-overlay, and new revisions of the gcc and llvm ebuilds must be
33 Copy over sources and `build.py` to chromiumos-overlay:
35 (chroot) /mnt/host/source/src/third_party/chromiumos-overlay/sys-devel/llvm/files/update_compiler_w…
38 Rename chromiumos-overlay/sys-devel/llvm/llvm-${VERSION}.ebuild to the next
40 11.0_pre394483_p20200618-r2:
42 (chroot) cd ~/trunk/src/third_party/chromiumos-overlay
43 (chroot) git mv llvm-11.0_pre394483_p20200618-r2.ebuild llvm-11.0_pre394483_p20200618-r3.ebuild
46 Rename chromiumos-overlay/sys-devel/gcc/gcc-${VERSION}.ebuild to the next
47 revision number.  For example, if the current version is 10.2.0-r3:
49 (chroot) cd ~/trunk/src/third_party/chromiumos-overlay
50 (chroot) git mv sys-devel/gcc/gcc-10.2.0-r3.ebuild sys-devel/gcc/gcc-10.2.0-r4.ebuild
63 - third_party/chromiumos-overlay/sys-devel/llvm/llvm-*.ebuild
64 - third_party/chromiumos-overlay/sys-devel/gcc/gcc-*.ebuild
68 - Sysroot wrapper with ccache:
69   `/usr/x86_64-pc-linux-gnu/<arch>/gcc-bin/10.2.0/sysroot_wrapper.hardened.ccache`
70 - Sysroot wrapper without ccache:
71   `/usr/x86_64-pc-linux-gnu/<arch>/gcc-bin/10.2.0/sysroot_wrapper.hardened.noccache`
72 - Clang host wrapper:
74 - Gcc host wrapper:
75   `/usr/x86_64-pc-linux-gnu/gcc-bin/10.2.0/host_wrapper`
79 When Clang crashes, its output can be extremely useful. Often, it will provide
83 clang-15: unable to execute command: Illegal instruction
84 clang-15: note: diagnostic msg: /tmp/clang_crash_diagnostics/foo-5420d2.c
85 clang-15: note: diagnostic msg: /tmp/clang_crash_diagnostics/foo-5420d2.sh
88 Where the artifacts at `/tmp/clang_crash_diagnostics/foo-*` are a full,
89 self-contained reproducer of the inputs that caused the crash in question.
91 _doesn't_ happen (e.g., maybe Clang is now emitting an error where it used to
93 collecting and crafting such a reproducer is a multi-step process, and can be
94 error-prone; compile commands may rely on env vars, they may be done within
99 Clang even on files that ordinarily don't cause Clang to crash. For various
102 tool for devs interested in creating a self-contained reproducer without having