Displaying 3 results from an estimated 3 matches for "collectpattern".
Did you mean:
collectpatterns
2013 May 19
1
[LLVMdev] Types vs. register classes in instruction patterns -- effect on FastISel
...or certain kinds of patterns
(function names containing .getPtrType() as a substring, etc.). ARM
couldn't build the .inc file at all due to duplicate patterns.
So I think we have to specifically recognize ValueTypes. To keep things
simple, we could pass in the destination register class from
collectPatterns, which has the output register class of the destination
pattern, and only permit a ValueType representable by that RC.
For an experiment, I tried allowing all ValueType source operands. This
had no effect on code generated for the ARM and X86 targets, so that's
good. However, I ran into pro...
2013 May 17
0
[LLVMdev] Types vs. register classes in instruction patterns -- effect on FastISel
On May 17, 2013, at 2:04 PM, Bill Schmidt <wschmidt at linux.vnet.ibm.com> wrote:
> Hello,
>
> In http://llvm.org/viewvc/llvm-project?view=revision&revision=177889 and
> http://llvm.org/viewvc/llvm-project?view=revision&revision=177890 (along
> with some follow-up patches) the PowerPC back end was changed to use
> types instead of register classes in instruction
2013 May 17
2
[LLVMdev] Types vs. register classes in instruction patterns -- effect on FastISel
Hello,
In http://llvm.org/viewvc/llvm-project?view=revision&revision=177889 and
http://llvm.org/viewvc/llvm-project?view=revision&revision=177890 (along
with some follow-up patches) the PowerPC back end was changed to use
types instead of register classes in instruction patterns. This matched
similar changes that Jakob made for Sparc in r177835.
I've recently come across an