search for: machinbememoperand

...e if one of your addressing compoenent is a vector, you have a gather-scatter situation. > What is the expected use case for "vector" operands that are not > registers? What do you plan to use this information for? Well, as I explained earlier, I wanted to add type information to MachinbeMemOperands so I could comment spills as either Vector or Scalar. That's less important now, so that's why I decided to drop that for the time being. I still think type information in the MachineMemOperand is a good idea because it preserves useful information longer. But I'll come back to that...

On Dec 4, 2009, at 2:44 PM, David Greene wrote: > Here's a reworked patch to mark instructions and operands as vector > or scalar. > It uses TableGen to infer the flags from types, allowing the user to > override > with a "let isVector = 0" clause. > > I decided to forego classifying MachineMemOperands for now in the > interests of > getting this

...nent is a vector, you have a gather-scatter > situation. > >> What is the expected use case for "vector" operands that are not >> registers? What do you plan to use this information for? > > Well, as I explained earlier, I wanted to add type information to > MachinbeMemOperands so I could comment spills as either Vector or > Scalar. That's less important now, so that's why I decided to > drop that for the time being. I still think type information in > the MachineMemOperand is a good idea because it preserves useful > information longer. But I'...

Here's a reworked patch to mark instructions and operands as vector or scalar. It uses TableGen to infer the flags from types, allowing the user to override with a "let isVector = 0" clause. I decided to forego classifying MachineMemOperands for now in the interests of getting this piece in. I still think we should add type information to MachineMemOperands. Why throw away