The current Cost Model implementation is very inaccurate and has to be updated, improved, re-implemented to be able to take into account the concrete CPU models and the concrete targets where this Cost Model is being used. For example, the Latency Cost Model should be differ from Code Size Cost Model, etc.
This patch is the first step to launch the developing and implementation of a new Cost Model generation.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
LGTM.
Regarding the TODO - if you're planning on starting work on this anytime soon, I feel it'd be a good idea to send an RFC about this to llvm-dev.
Having the cost model specialized for different targets seems like a very large change, and we probably need wider discussion of what exactly this'll look like.
Comment Actions
About TODO: of course we're going to prepare RFC for public discussions before real start of work.
following