dag at cray.com
Wed Dec 2 15:03:46 PST 2009
On Wednesday 02 December 2009 01:26, Chris Lattner wrote:
> > Yes, I've written all that support. But that doesn't cover
> > MachineMemOperands. AFAIK there's no machine-independent way to tell
> > which instruction operands make up a MachineMemOperand. And even then,
> > that would only tell you about the compoenents that make up the address,
> > not the data itself. Note that having a machine-independent way to
> > associate MachineOperands with MachineMemOperands would also be highly
> > useful, but that will come later.
> Again, you're saying that you need something without explaining what for.
No, no, I don't need this particular mapping. What I need is information to
determine whether a MachineMemOperand is of vector type. Hence the EVT
would be useful. I don't care right now which MachineOperands it aggregates.
More information about the llvm-dev