RPCS3/llvm-mirror
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-10-19 02:52:53 +02:00
Code Issues Projects Releases Wiki Activity
1bdf10a116
llvm-mirror/lib/Analysis/models/inliner
History
Mircea Trofin 3359e4e021 [MLInliner] In development mode, obtain the output specs from a file 
Different training algorithms may produce models that, besides the main
policy output (i.e. inline/don't inline), produce additional outputs
that are necessary for the next training stage. To facilitate this, in
development mode, we require the training policy infrastructure produce
a description of the outputs that are interesting to it, in the form of
a JSON file. We special-case the first entry in the JSON file as the
inlining decision - we care about its value, so we can guide inlining
during training - but treat the rest as opaque data that we just copy
over to the training log.

Differential Revision: https://reviews.llvm.org/D85674
2020-08-17 16:56:47 -07:00
..
variables
output_spec.json [MLInliner] In development mode, obtain the output specs from a file 2020-08-17 16:56:47 -07:00
README.txt [NFC]{MLInliner] Point out the tests' model dependencies 2020-08-06 09:57:26 -07:00
saved_model.pbtxt

README.txt 

Reference model for inliner -Oz decision policy.
Note that, currently, this model is also referenced by test/Transforms/Inline/ML
tests - if replacing it, check those tests, too.