Lines Matching +full:built +full:- +full:docs

11 has a mostly linear history, it has a few merge commits that added projects --
14 toplevel project that was developed out-of-tree and then merged later.
21 See https://git-scm.com/docs/git-bisect for a good overview. In summary:
23   .. code-block:: bash
36 being able to reset, do the usual ``git checkout -f main; git reset --hard
43 a large code base with just-built clang. This can take a long time, so it's
46 automatically. Writing the script can take 10-20 minutes, but it's almost
47 always worth it -- you can do something else while the bisect runs (such
50 Here's an example run script. It assumes that you're in ``llvm-project`` and
51 that you have a sibling ``llvm-build-project`` build directory where you
56   .. code-block:: bash
60      ninja -C ../llvm-build-project clang || exit 125
62      ../llvm-build-project/bin/clang repro.c
68 ./run.sh``. Don't forget to mark your run script as executable -- ``git bisect
74 (This is a very simple run script. Often, you want to use just-built clang
75 to build a different project and then run a built executable of that project
83   .. code-block:: none
85      A-o-o-......-o-D-o-o-HEAD
87        B-o-...-o-C-
108 If you know the bug is due to a change in llvm, clang, or compiler-rt, use
110   .. code-block:: bash
112      git bisect start -- clang llvm compiler-rt
125 https://git-scm.com/book/en/v2/Git-Tools-Revision-Selection