Displaying 10 results from an estimated 10 matches for "parseconstraints".
2010 Aug 25
2
[LLVMdev] [REQUEST FOR FEEDBACK] Inline asm multiple alternative constraints
...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 internals), which
meant that I needed to handle multiple alternat...
2010 Aug 27
0
[LLVMdev] [REQUEST FOR FEEDBACK] Inline asm multiple alternative constraints
...rse 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
> familiar yet with LLVM internals), which meant that I needed...
2010 Aug 30
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
>> think there is, as I'm not too familiar yet with LLVM internals), which
>> meant that...
2010 Aug 30
0
[LLVMdev] [REQUEST FOR FEEDBACK] Inline asm multiple alternative constraints
...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
> familiar yet with LLVM internals), which meant that I needed...
2010 Aug 30
2
[LLVMdev] [REQUEST FOR FEEDBACK] Inline asm multiple alternative constraints
...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 internals), which
>>...
2010 Sep 01
2
[LLVMdev] [REQUEST FOR FEEDBACK] Inline asm multiple alternative constraints
...s.
>>>>
>>>> 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 internals), wh...
2010 Aug 30
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 don't think there is, as I'm not too
>> familiar yet with LLVM internals), which mea...
2010 Sep 02
2
[LLVMdev] [REQUEST FOR FEEDBACK] Inline asm multiple alternative constraints
...gt;
>>>>> 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 in...
2010 Sep 02
0
[LLVMdev] [REQUEST FOR FEEDBACK] Inline asm multiple alternative constraints
...e 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 inter...
2010 Sep 02
0
[LLVMdev] [REQUEST FOR FEEDBACK] Inline asm multiple alternative constraints
...gt;>> 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
>&g...