diff options
author | Kazu Hirata <kazu@google.com> | 2022-12-15 11:11:24 -0800 |
---|---|---|
committer | Kazu Hirata <kazu@google.com> | 2022-12-15 11:11:24 -0800 |
commit | 9112ec6ad0593b067762ae24a036d207f689c78a (patch) | |
tree | 44f3b1bd71d2d5268010f3946fb9c484678cdcc1 /llvm/unittests/Analysis/ValueTrackingTest.cpp | |
parent | 23f4f66da7c0ed83f3435cb8e87f54740c9fb3c3 (diff) | |
download | llvm-9112ec6ad0593b067762ae24a036d207f689c78a.zip llvm-9112ec6ad0593b067762ae24a036d207f689c78a.tar.gz llvm-9112ec6ad0593b067762ae24a036d207f689c78a.tar.bz2 |
[mlgo] Use LLVM_HAVE_TFLITE instead of LLVM_HAVE_TF_API
This patch replaces uses of LLVM_HAVE_TF_API with LLVM_HAVE_TFLITE in
a couple of CMakeLists.txt.
Now that 842b0d0fe2dd142305a9461e50cdce9aff7f86bc has landed,
we now have:
LLVM_HAVE_TF_API is defined if and only if LLVM_HAVE_TFLITE
evaluates to true
in the CMake variable world (assuming that you do not set
LLVM_HAVE_TF_API on the cmake invocation).
FWIW, the story is a little different in the C++ macro world, where:
LLVM_HAVE_TF_API is defined if and only if LLVM_HAVE_TFLITE is
defined
This is why edc83a15b45e6b91fce3f35622a6b0a6d34e5211 consisted only of
mechanical replacements.
Differential Revision: https://reviews.llvm.org/D140061
Diffstat (limited to 'llvm/unittests/Analysis/ValueTrackingTest.cpp')
0 files changed, 0 insertions, 0 deletions