1 Ideas for things to do:
3 - more projects (lldb, check- targets for compiler-rt's asan/ubsan/msan/tsan)
4 - once there are more projects, have an llvm_enable_projects arg, modeled
5 after llvm_targets_to_build in the GN build
6 - a check-all build target that runs test of all projects
7 - more targets (ARC MSP430 XCore)
8 - example: https://reviews.llvm.org/D56416
9 - investigate feasibility of working `gn check`
11 - "optimized tblgen" mode
12 - either just always build tablegen and support with opt config
13 - or use opt toolchain and build tablegen twice in debug builds, like cmake
15 - cross builds using GN's toolchain feature
17 - move clang_tablegen into lib/ for private files
18 - add dead code stripping
19 - move run_tablegen.py from build to tablegen folder
20 - figure out why -Iclang/Support gets added so often
21 => https://groups.google.com/a/chromium.org/forum/?oldui=1#!msg/gn-dev/0S7KRGIXcDI/E4ahA1jQFQAJ
22 => Fixed in https://gn-review.googlesource.com/c/gn/+/11701 !
23 `llvm/utils/gn/get.py` to get new gn binary with the fix
24 - plugin() template with working rpath, exports thingers
25 - then port clang_build_examples and enable by default so that clang
26 plugin tests run by default
27 - plugin_host() template