tree 123a7abf2ebb28d194dac688d8c1653142a341ad
parent cea68eff372355e80d74993d0d2262a8ae7e8d3b
author Geoffrey Martin-Noble <gcmn@google.com> 1602097600 -0700
committer GitHub <noreply@github.com> 1602097600 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJffhHACRBK7hj4Ov3rIwAAdHIIAKDKbb6OQkTbKAAYftheBFSW
 KXkT4RBtz5VX+ABebpnqaPplu5G4JXrw5u6WpRRcsRI8TFZhWn1aBVJF7SGONrNX
 K9+DMoU09jQDrwfA7IKWNusdJ6Ot/0IvsTaZoMtoekPkcdHwM6Pe3/rucIqkCtFy
 TBVR7PjuHAZExRXdjx8Oq9AyULAaGJyrdGRFLtWah4w9fe1Ejdbyj6K36oJOCJp5
 IqKsyAP9B0gzf/gnLf/BxBnH2s5KHzIoLQJ+7RTKM9fvw5oSQYTD8q83UF5poLO2
 mINYFsJXz+usgEdAIC5534jQCLs2kFgLD3s6qPLZYAdumnhtrj+spEnpHGfSUYg=
 =spge
 -----END PGP SIGNATURE-----
 

Use LLVM Bazel BUILD files from google/llvm-bazel (#2794)

Adopts build files from https://github.com/google/llvm-bazel.

These make our LLVM build independent of TensorFlow. Switching to them
does slightly increase maintenance burden on our team because the TF
team is not assisting in maintaining them. It is not a guarantee that
llvm-bazel will already have a commit containing the up to date
workflows. However, it does have an advertised tag for each LLVM commit
that is the current best-effort for what builds, a workflow to
automatically pull in new LLVM commits and a build pipeline that
notifies me as soon as the build breaks (independent of any integration
into Google source control).

For example https://github.com/google/llvm-bazel/commit/0fc76899f74a
advances the build files ahead of what is currently supported by TF or
Google internally.

I will be expanding our build cop docs to cover more of the workflows
here as I am buildcopping this week, but the general workflow is to run
`./scripts/git/update_llvm_dependent_submodules.sh` in lieu of the
update old `update_tf_submodule.sh` script. A GitHub action will also
create those PRs automatically to be merged.