search for: vninfolist

...huge function. If it's a coalescing bug it's probably in my code since I'm not using the current default llvm coalescer. It may be that I'm updating dataflow information incorrectly. I'll check on that. > > If so, then isn't LiveInterval::Ranges and LiveInterval::VNInfoList > > redundant? > > What's in VNInfoList that's not in the valno member of the Ranges > > elements, > > and vice-versa? > > I am not sure if I understand your question. Multiple liveranges can > be of the same val#. Each VNInfo contains definition (if not &gt...

...k. It could be a bug. Can you get me a test case? > > > A related question: LiveRange::valno is a single value, correct? In > other > words it doesn't point to an array or anything, right? Correct. > > > If so, then isn't LiveInterval::Ranges and LiveInterval::VNInfoList > redundant? > What's in VNInfoList that's not in the valno member of the Ranges > elements, > and vice-versa? I am not sure if I understand your question. Multiple liveranges can be of the same val#. Each VNInfo contains definition (if not containing a phi merge, etc.)...

...%reg1055 doesn't appear anywhere else in the program so it shouldn't be live-in to the block. A related question: LiveRange::valno is a single value, correct? In other words it doesn't point to an array or anything, right? If so, then isn't LiveInterval::Ranges and LiveInterval::VNInfoList redundant? What's in VNInfoList that's not in the valno member of the Ranges elements, and vice-versa? -Dave