aboutsummaryrefslogtreecommitdiff
path: root/llvm/tools/llvm-libtool-darwin/llvm-libtool-darwin.cpp
diff options
context:
space:
mode:
authorUtkarsh Saxena <usx@google.com>2020-10-23 10:19:53 +0200
committerUtkarsh Saxena <usx@google.com>2020-10-29 19:49:40 +0100
commit7df80a1204f0dc91fb8bba7635e2354adf08989f (patch)
treec577434aa85649a84bac70ee202e545ee0644885 /llvm/tools/llvm-libtool-darwin/llvm-libtool-darwin.cpp
parent22c38376345670c1883963e5e1cccd597a15b3a5 (diff)
downloadllvm-7df80a1204f0dc91fb8bba7635e2354adf08989f.zip
llvm-7df80a1204f0dc91fb8bba7635e2354adf08989f.tar.gz
llvm-7df80a1204f0dc91fb8bba7635e2354adf08989f.tar.bz2
[clangd] Add support for multiple DecisionForest model experiments.
With every incremental change, one needs to check-in new model upstream. This also significantly increases the size of the git repo with every new model. Testing and comparing the old and previous model is also not possible as we run only a single model at any point. One solution is to have a "staging" decision forest which can be injected into clangd without pushing it to upstream. Compare the performance of the staging model with the live model. After a couple of enhancements have been done to staging model, we can then replace the live model upstream with the staging model. This reduces upstream churn and also allows us to compare models with current baseline model. This is done by having a callback in CodeCompleteOptions which is called only when we want to use a decision forest ranking model. This allows us to inject different completion model internally. Differential Revision: https://reviews.llvm.org/D90014
Diffstat (limited to 'llvm/tools/llvm-libtool-darwin/llvm-libtool-darwin.cpp')
0 files changed, 0 insertions, 0 deletions