This prepares it for logging externally-specified outputs.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Event Timeline
llvm/lib/Analysis/DevelopmentModeInlineAdvisor.cpp | ||
---|---|---|
107 | This is what typed cases call - e.g. when we log the feature tensors. We know their type at compile time. It saves us from typecasting all the time the data buffer. | |
123–138 | don't think it'll add much value, there are just the 3 cases, because of the limitation in what the Feature protobuf supports. Also there's the int32_t special casing. | |
162 | No, and we may actually yank out Effects - we don't currently use it. | |
382–384 | Maybe, but we need to evaluate that alternative. Effects should be the same as decision, except if somehow inlining failed for a correctness reason we didn't detect upfront. So training, currently, may end up being confused by this aspect. |
when we will be using this?