[PATCH] D85674: [MLInliner] In development mode, obtain the output specs from a file

[Mircea Trofin via Phabricator via llvm-commits]

mtrofin created this revision.
mtrofin added reviewers: davidxl, yundiqian, ebrevdo.
Herald added subscribers: llvm-commits, hiraditya, eraman.
Herald added a project: LLVM.
mtrofin requested review of this revision.

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.


Repository:
  rG LLVM Github Monorepo

https://reviews.llvm.org/D85674

Files:
  llvm/lib/Analysis/DevelopmentModeInlineAdvisor.cpp
  llvm/lib/Analysis/models/inliner/output_spec.json
  llvm/test/Transforms/Inline/ML/Inputs/test_output_spec.json
  llvm/test/Transforms/Inline/ML/development-training-log.ll

-------------- next part --------------
A non-text attachment was scrubbed...
Name: D85674.284455.patch
Type: text/x-patch
Size: 14891 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20200810/296ae585/attachment.bin>