search for: registercoalecer

...it necessary to separate class InterferenceData out from > RegisterCoalescer.h? Good point. Originally I had thought that InterferenceData might be more general-purpose but it is rather coalescing-specific at the moment. If this changes in the future we can break it out. I'll keep it in RegisterCoalecer.h. > 5. > + /// Run the coalescer on this function, providing interference > + /// data to query. Return whether we removed any copies. > + virtual bool coalesceFunction(MachineFunction &mf, > InterferenceData &ifd) = 0; > > 80 col violation. Ok. > 6. &g...

...terferenceData out from >> RegisterCoalescer.h? > > Good point. Originally I had thought that InterferenceData might be > more general-purpose but it is rather coalescing-specific at the > moment. > If this changes in the future we can break it out. I'll keep it in > RegisterCoalecer.h. > >> 5. >> + /// Run the coalescer on this function, providing interference >> + /// data to query. Return whether we removed any copies. >> + virtual bool coalesceFunction(MachineFunction &mf, >> InterferenceData &ifd) = 0; >> >> 80...

Hi David, Thanks for this patch! Some comments: 1. typedef std::set<const LiveInterval *> IntervalSet; Please use SmallPtrSet instead. 2. + virtual void mergeIntervals(const LiveInterval &a, + const LiveInterval &b, + const MachineInstr &copy) {}; I find the name misleading. It's not actually

Here's a proposed patch for reworking register coalescing to allow pluggable coalescers. I think I've got the interfaces where I want them and am reasonably sure I've squashed most of the bugs. I'm still doing some testing and want to get through a whole regimen before committing. As a reminder, this patch has several goals: - Allow user-specified register coalescers, similar