search for: targetfooimpl

...e the default implementation is in CodeGen while target overridden version are in Target. I also hate to see all these Target* classes being moved to CodeGen. > > I thought our solution to this issue is classes such as TargetInstrInfoImpl. What's wrong with it? I wasn't familiar with TargetFooImpl when I sent out the initial mail. I don't like it because it splits the implementation of the class across two entirely separate libraries (not merely source files), it's easy to accidentally regress the dependency, it doesn't make sense to have two target-independent layers especially...

I have mixed feeling about this. While this does separate out target-independent pieces into CodeGen, it also introduces some confusion where the default implementation is in CodeGen while target overridden version are in Target. I also hate to see all these Target* classes being moved to CodeGen. I thought our solution to this issue is classes such as TargetInstrInfoImpl. What's wrong with