History log of /external/tensorflow/tensorflow/compiler/xla/service/cpu/external_constant_pool.h
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
f8347ceebbad0e06552633fcdf8e63f52246ba62 24-Jan-2018 Sanjoy Das <sanjoy@google.com> Remove THIRD_PARTY_ from #include guards

They don't make sense in the open source repository.

PiperOrigin-RevId: 183140889
/external/tensorflow/tensorflow/compiler/xla/service/cpu/external_constant_pool.h
20765b3e1ae3b718699592c98aa9805cb874b6d1 29-Dec-2017 Patrick Nguyen <drpng@google.com> Merge changes from github.

PiperOrigin-RevId: 180301735
/external/tensorflow/tensorflow/compiler/xla/service/cpu/external_constant_pool.h
effb22e8a44763901ee2cf55c30290f0b1edb570 10-Oct-2017 Sanjoy Das <sanjoy@google.com> Use an external constant pool to reduce LLVM compile times

LLVM does not deal well with huge arrays emitted inline into the IR. In JIT
mode, this change teaches XLA to emit large constant tensors onto a side data
structure, which are then symbolically linked to the generated executable. It
is important to note that this works only in JIT mode, and my current
understanding is that making this work reliably in AOT will be somewhat more
difficult.

PiperOrigin-RevId: 171626043
/external/tensorflow/tensorflow/compiler/xla/service/cpu/external_constant_pool.h