search for: computeconstrainttouse

...llvm::CallSite, llvm::DenseMap<llvm::Value*, llvm::Value*, llvm::DenseMapInfo<llvm::Value*>, llvm::DenseMapInfo<llvm::Value*> >&)’: /Volumes/mrs5/net/llvm/llvm/lib/Transforms/Scalar/CodeGenPrepare.cpp: 966: error: no matching function for call to ‘llvm::TargetLowering::ComputeConstraintToUse (llvm::TargetLowering::AsmOperandInfo&, llvm::SDValue) const’ /Volumes/mrs5/net/llvm/llvm/include/llvm/Target/TargetLowering.h:1177: note: candidates are: virtual void llvm::TargetLowering::ComputeConstraintToUse (llvm::TargetLowering::AsmOperandInfo&, llvm::SDValue, bool, llvm::Sel...

...lang change is to output the multiple constraints using a '|' character in the constraint strings to delimit the alternatives. The LLVM change is as follows. In an earlier attempt, I just hacked up SelectionDAGBuilder::visitInlineAsm, and pretty much used the same logic in TargetLowering::ComputeConstraintToUse/ChooseConstraint. But then I discovered that InlineAsm::ParseConstraints was called in a couple of other places, and in one of those places (IsOperandAMemoryOperand in AddrModeMatcher.cpp), there wasn't a DAG pointer handy (at least I don't think there is, as I'm not too familiar yet w...

...raint strings to delimit the alternatives. This part is simple, and it can't be worse than it is now. > The LLVM change is as follows. > > In an earlier attempt, I just hacked up > SelectionDAGBuilder::visitInlineAsm, and pretty much used the same > logic in TargetLowering::ComputeConstraintToUse/ChooseConstraint. > But then I discovered that InlineAsm::ParseConstraints was called in > a couple of other places, and in one of those places > (IsOperandAMemoryOperand in AddrModeMatcher.cpp), there wasn't a DAG > pointer handy (at least I don't think there is, as I&...

...s. >> > > This part is simple, and it can't be worse than it is now. > > > The LLVM change is as follows. >> >> In an earlier attempt, I just hacked up >> SelectionDAGBuilder::visitInlineAsm, and pretty much used the same logic in >> TargetLowering::ComputeConstraintToUse/ChooseConstraint. But then I >> discovered that InlineAsm::ParseConstraints was called in a couple of other >> places, and in one of those places (IsOperandAMemoryOperand in >> AddrModeMatcher.cpp), there wasn't a DAG pointer handy (at least I don't >> think there i...

...elimit the alternatives. > > This part is simple, and it can't be worse than it is now. > > > The LLVM change is as follows. > > In an earlier attempt, I just hacked up > SelectionDAGBuilder::visitInlineAsm, and pretty much used the same > logic in TargetLowering::ComputeConstraintToUse/ChooseConstraint. > But then I discovered that InlineAsm::ParseConstraints was called in > a couple of other places, and in one of those places > (IsOperandAMemoryOperand in AddrModeMatcher.cpp), there wasn't a DAG > pointer handy (at least I don't think there is, as I&...

...part is simple, and it can't be worse than it is now. >> >> >> The LLVM change is as follows. >>> >>> In an earlier attempt, I just hacked up >>> SelectionDAGBuilder::visitInlineAsm, and pretty much used the same logic in >>> TargetLowering::ComputeConstraintToUse/ChooseConstraint. But then I >>> discovered that InlineAsm::ParseConstraints was called in a couple of other >>> places, and in one of those places (IsOperandAMemoryOperand in >>> AddrModeMatcher.cpp), there wasn't a DAG pointer handy (at least I don't >>&g...

...39;t be worse than it is now. >>> >>> >>> The LLVM change is as follows. >>>> >>>> In an earlier attempt, I just hacked up >>>> SelectionDAGBuilder::visitInlineAsm, and pretty much used the same logic in >>>> TargetLowering::ComputeConstraintToUse/ChooseConstraint. But then I >>>> discovered that InlineAsm::ParseConstraints was called in a couple of other >>>> places, and in one of those places (IsOperandAMemoryOperand in >>>> AddrModeMatcher.cpp), there wasn't a DAG pointer handy (at least I don'...

...t;> This part is simple, and it can't be worse than it is now. >> >> >> The LLVM change is as follows. >> >> In an earlier attempt, I just hacked up >> SelectionDAGBuilder::visitInlineAsm, and pretty much used the same >> logic in TargetLowering::ComputeConstraintToUse/ChooseConstraint. >> But then I discovered that InlineAsm::ParseConstraints was called >> in a couple of other places, and in one of those places >> (IsOperandAMemoryOperand in AddrModeMatcher.cpp), there wasn't a >> DAG pointer handy (at least I don't think...

.... >>>> >>>> >>>> The LLVM change is as follows. >>>>> >>>>> In an earlier attempt, I just hacked up >>>>> SelectionDAGBuilder::visitInlineAsm, and pretty much used the same logic in >>>>> TargetLowering::ComputeConstraintToUse/ChooseConstraint. But then I >>>>> discovered that InlineAsm::ParseConstraints was called in a couple of other >>>>> places, and in one of those places (IsOperandAMemoryOperand in >>>>> AddrModeMatcher.cpp), there wasn't a DAG pointer handy (at leas...

...and it can't be worse than it is now. >>> >>> >>> The LLVM change is as follows. >>> >>> In an earlier attempt, I just hacked up >>> SelectionDAGBuilder::visitInlineAsm, and pretty much used the same >>> logic in TargetLowering::ComputeConstraintToUse/ChooseConstraint. >>> But then I discovered that InlineAsm::ParseConstraints was called >>> in a couple of other places, and in one of those places >>> (IsOperandAMemoryOperand in AddrModeMatcher.cpp), there wasn't a >>> DAG pointer handy (at least I...

...an it is now. >>>> >>>> >>>> The LLVM change is as follows. >>>> >>>> In an earlier attempt, I just hacked up >>>> SelectionDAGBuilder::visitInlineAsm, and pretty much used the >>>> same logic in TargetLowering::ComputeConstraintToUse/ >>>> ChooseConstraint. But then I discovered that >>>> InlineAsm::ParseConstraints was called in a couple of other >>>> places, and in one of those places (IsOperandAMemoryOperand in >>>> AddrModeMatcher.cpp), there wasn't a DAG pointer h...