[all-commits] [llvm/llvm-project] 62fc44: [MLInliner] In development mode, obtain the output...

[Mircea Trofin via All-commits]

  Branch: refs/heads/master
  Home:   https://github.com/llvm/llvm-project
  Commit: 62fc44ca3cf66442b30e22b1be34afc492a2a388
      https://github.com/llvm/llvm-project/commit/62fc44ca3cf66442b30e22b1be34afc492a2a388
  Author: Mircea Trofin <mtrofin at google.com>
  Date:   2020-08-17 (Mon, 17 Aug 2020)

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

  Log Message:
  -----------
  [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