Displaying 4 results from an estimated 4 matches for "r509".
Did you mean:
509
2016 Aug 22
3
Instruction itineraries and fence/barrier instructions
...call void @llvm.xstg.memory.barrier(i32 2, i8 0)
%1 = load volatile i32* @read_me, align 4
ret i32 %1
}
Prior to adding our instruction itineraries the code generated was:
xstg_intrinsic: # @xstg_intrinsic
# BB#0: # %entry
subI r509, r509, 16, 64
store r510, r509, 0, 64
bitop1 r510, r509, 0, OR, 64
store r0, r510, 12, 32
movimm r1, %hi(write_me), 64
movimmshf32 r1, r1, %lo(write_me)
store r0, r1, 0, 32
fence 2
movimm r0, %hi(read_me), 64
movimmshf...
2016 Aug 22
2
Instruction itineraries and fence/barrier instructions
...@read_me, align 4
> > ret i32 %1
> > }
> >
> > Prior to adding our instruction itineraries the code generated was:
> >
> > xstg_intrinsic: # @xstg_intrinsic
> > # BB#0: # %entry
> > subI r509, r509, 16, 64
> > store r510, r509, 0, 64
> > bitop1 r510, r509, 0, OR, 64
> > store r0, r510, 12, 32
> > movimm r1, %hi(write_me), 64
> > movimmshf32 r1, r1, %lo(write_me)
> > store r0, r1, 0, 32
>...
2016 Jan 07
2
TableGen error message: top-level forms in instruction pattern should have void types
...*, align 8
store i32 %argc, i32* %argc.addr, align 4
store i8** %argv, i8*** %argv.addr, align 8
%0 = load i32 addrspace(4)* @answer, align 4
store i32 %0, i32* @xint, align 4
...
Currently this produces the following assembly code:
.Ltmp0:
.cfi_def_cfa_offset 48
store r510, r509, 0, 64
.Ltmp1:
.cfi_offset 510, -48
bitop1 r510, r509, 0, OR, 64
.Ltmp2:
.cfi_def_cfa_register 510
store r0, r510, 44, 32
store r1, r510, 32, 64
movimm r0, %hi(xint), 64
movimmshf32 r0, r0, %lo(xint)
movimm r1, %rel(answer), 64...
2016 Jan 07
2
TableGen error message: top-level forms in instruction pattern should have void types
On Thu, Jan 7, 2016 at 12:21 PM, Krzysztof Parzyszek via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> On 1/7/2016 1:55 PM, Phil Tomson via llvm-dev wrote:
>
>>
>> let Uses= [GRP] in {
>> def RelAddr : XSTGPseudo< (outs),
>> (ins GPRC:$spoff, GPRC:$dst),
>>