Displaying 6 results from an estimated 6 matches for "w19".
Did you mean:
19
2015 Feb 19
2
[LLVMdev] ScheduleDAGInstrs computes deps using IR Values that may be invalid
...-------------------------------------------------------------------------
BB#14: derived from LLVM BB %if.end.1
Live Ins: %X16 %X17 %X18 %X7 %X0 %X6 %X4 %W8 %X15 %X14 %W3 %W2 %X1
%X10 %X11 %X12 %X13 %X9
Predecessors according to CFG: BB#12
%X5<def> = ADDXrr %X16, %X13
* %W19<def> = LDRBBui %X5, 1; mem:LD1[%scevgep95](tbaa=<0x6e02518>)
* %W3<def> = MADDWrrr %W2<kill>, %W3<kill>, %WZR
* %W2<def> = SUBWrr %W3<kill>, %W19<kill>
* STRBBui %W2<kill>, %X5<kill>, 1;
mem:ST1[%scevgep95](tbaa=<0x6e0...
2018 Dec 05
2
Strange regalloc behaviour: one more available register causes much worse allocation
...patch is not correct, but it happens to be a useful way of
provoking the problem.
Without the patch generating assembly with llc -mcpu=cortex-a57 everything looks
fine, but with the patch we get this (which comes from the block
bb.17.switchdest13):
.LBB0_16:
mov x29, x24
mov w24, w20
mov w20, w19
mov w19, w7
mov w7, w6
mov w6, w5
mov w5, w2
mov x2, x18
mov w18, w15
orr w15, wzr, #0x1c
str w15, [x8, #8]
mov w0, wzr
mov w15, w18
mov x18, x2
mov w2, w5
mov w5, w6
mov w6, w7
mov w7, w19
mov w19, w20
mov w20, w24
mov x24, x29
b .LBB0_3
It looks like the orr and str have barge...
2018 Dec 05
3
Strange regalloc behaviour: one more available register causes much worse allocation
...pens to be a useful way of
provoking the problem.
Without the patch generating assembly with llc -mcpu=cortex-a57 everything looks
fine, but with the patch we get this (which comes from the block
bb.17.switchdest13):
.LBB0_16:
mov x29, x24
mov w24, w20
mov w20, w19
mov w19, w7
mov w7, w6
mov w6, w5
mov w5, w2
mov x2, x18
mov w18, w15
orr w15, wzr, #0x1c
str w15, [x8, #8]
mov w0, wzr
mov w15, w18
mov x18, x2
mov w2, w5...
2010 Dec 17
3
Alternative to extended recode sintax?
Dear R-users,
I have a factor variable within my data frame which I derive week after week from a POSIXct variable using the cut(var,"weeks") command I have found in the chron package. The levels() command gives me:
[1] "2009-03-30 00:00:00" "2009-04-06 00:00:00" "2009-04-13 00:00:00" "2009-04-20 00:00:00" "2009-04-27 00:00:00"
2015 May 06
2
[LLVMdev] [lld] Wrong references for C++ COMDAT groups
...ndefined
Where it should be:
0000000000000000 <_Z4funcj>:
0: a9bd57f6 stp x22, x21, [sp,#-48]!
4: a9014ff4 stp x20, x19, [sp,#16]
8: a9027bfd stp x29, x30, [sp,#32]
c: 910083fd add x29, sp, #0x20
10: 2a0003f3 mov w19, w0
And there is no relocation (static or dynamic) point to the faulty instruction.
It exist, however, a group section relocation with same offset, but for a
different text segments (the exception handler stub create by clang):
Relocation section '.rela.text' at offset 0xed8 contains 2 en...
2015 May 07
2
[LLVMdev] [lld] Wrong references for C++ COMDAT groups
...00 <_Z4funcj>:
> 0: a9bd57f6 stp x22, x21, [sp,#-48]!
> 4: a9014ff4 stp x20, x19, [sp,#16]
> 8: a9027bfd stp x29, x30, [sp,#32]
> c: 910083fd add x29, sp, #0x20
> 10: 2a0003f3 mov w19, w0
>
> And there is no relocation (static or dynamic) point to the faulty instruction.
> It exist, however, a group section relocation with same offset, but for a
> different text segments (the exception handler stub create by clang):
>
> Relocation section '...