search for: canonicalizationmodel

...other information. I think 'metrics' is a bad term to use in the API / pass. If it's about cost or metrics, than TTI makes too much sense. I would really like to get the fundamental idea of canonicalization into the API so that we correctly skew the design in that direction. Does "CanonicalizationModel" work? Is there some other way to phrase the types of queries that will make this more clear? I think phrasing this in terms of "target independent" is a bit of a trap -- if it looks at the data layout, it's not going to be independent... But I think I know what you're aimin...

I want to expose most of the logic in NoTTI to passes that do not depend on TTI for the purpose of pure IR-level instruction metrics. For example, we don't want the presence of certain "free" intrinsics to affect the patterns handled by canonical transforms. It would still be ok to use DataLayout here, so certain casts are considered free. The idea of "free" here has little