search for: chooseconstraint

Displaying 10 results from an estimated 10 matches for "chooseconstraint".

2010 Aug 25
2
[LLVMdev] [REQUEST FOR FEEDBACK] Inline asm multiple alternative constraints
...t 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 with LLVM internal...
2010 Aug 27
0
[LLVMdev] [REQUEST FOR FEEDBACK] Inline asm multiple alternative constraints
...t 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'm not too &...
2010 Aug 30
2
[LLVMdev] [REQUEST FOR FEEDBACK] Inline asm multiple alternative constraints
...his 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'm not...
2010 Aug 30
0
[LLVMdev] [REQUEST FOR FEEDBACK] Inline asm multiple alternative constraints
.... > > 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'm not too &...
2010 Aug 30
2
[LLVMdev] [REQUEST FOR FEEDBACK] Inline asm multiple alternative constraints
...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...
2010 Sep 01
2
[LLVMdev] [REQUEST FOR FEEDBACK] Inline asm multiple alternative constraints
...s 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 >>>&gt...
2010 Aug 30
0
[LLVMdev] [REQUEST FOR FEEDBACK] Inline asm multiple alternative constraints
...ple, 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...
2010 Sep 02
2
[LLVMdev] [REQUEST FOR FEEDBACK] Inline asm multiple alternative constraints
...>>> >>>> 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 &gt...
2010 Sep 02
0
[LLVMdev] [REQUEST FOR FEEDBACK] Inline asm multiple alternative constraints
...se 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...
2010 Sep 02
0
[LLVMdev] [REQUEST FOR FEEDBACK] Inline asm multiple alternative constraints
...;> >>>> 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...