Displaying 6 results from an estimated 6 matches for "_z3foopi".
Did you mean:
_z3fooii
2016 Mar 24
4
attribute of intrinsic function
...t;[], [llvm_ptr_ty], [IntrReadWriteArgMem]>;
def int_foo6 : Intrinsic<[], [llvm_ptr_ty], []>;
Then I write a very simple module, in each module the intrinsic function is
called twice as shown below:
/******the intrinsic function foo5 is used******/
; Function Attrs: nounwind
define void @_Z3fooPi(i8* %a) #0 {
call void @llvm.foo5(i8* %a)
call void @llvm.foo5(i8* %a)
ret void
}
; Function Attrs: nounwind
declare void @llvm.foo5(i8*) #0
attributes #0 = { nounwind }
/****** the intrinsic function foo6 is used******/
; Function Attrs: nounwind
define void @_Z3fooPi(i8* %a) #0 {
call v...
2016 Mar 24
0
attribute of intrinsic function
...ArgMem]>;
> def int_foo6 : Intrinsic<[], [llvm_ptr_ty], []>;
>
> Then I write a very simple module, in each module the intrinsic function is called twice as shown below:
>
> /******the intrinsic function foo5 is used******/
> ; Function Attrs: nounwind
> define void @_Z3fooPi(i8* %a) #0 {
> call void @llvm.foo5(i8* %a)
> call void @llvm.foo5(i8* %a)
> ret void
> }
> ; Function Attrs: nounwind
> declare void @llvm.foo5(i8*) #0
> attributes #0 = { nounwind }
I'd expect foo4 to have the "argmemonly" attribute.
How did you generate...
2016 Mar 24
0
attribute of intrinsic function
...em]>;
> def int_foo6 : Intrinsic<[], [llvm_ptr_ty], []>;
>
> Then I write a very simple module, in each module the intrinsic
> function is called twice as shown below:
>
> /******the intrinsic function foo5 is used******/
> ; Function Attrs: nounwind
> define void @_Z3fooPi(i8* %a) #0 {
> call void @llvm.foo5(i8* %a)
> call void @llvm.foo5(i8* %a)
> ret void
> }
> ; Function Attrs: nounwind
> declare void @llvm.foo5(i8*) #0
> attributes #0 = { nounwind }
This is strange. I would expect this to introduce the argmemonly
attribute. Can you c...
2016 Mar 25
1
attribute of intrinsic function
...Mem]>;
> def int_foo6 : Intrinsic<[], [llvm_ptr_ty], []>;
>
> Then I write a very simple module, in each module the intrinsic function
> is called twice as shown below:
>
> /******the intrinsic function foo5 is used******/
> ; Function Attrs: nounwind
> define void @_Z3fooPi(i8* %a) #0 {
> call void @llvm.foo5(i8* %a)
> call void @llvm.foo5(i8* %a)
> ret void
> }
> ; Function Attrs: nounwind
> declare void @llvm.foo5(i8*) #0
> attributes #0 = { nounwind }
>
> This is strange. I would expect this to introduce the argmemonly
> attribu...
2017 Jan 31
2
llvm.read_register for %RIP on x86_64
On Tue, Jan 31, 2017 at 3:11 PM, Renato Golin <renato.golin at linaro.org>
wrote:
> On 31 Jan 2017 8:58 p.m., "Kostya Serebryany" <kcc at google.com> wrote:
>
> hmm. I am not sure I understood you. The last two paragraphs seem to
> contradict each other.
> So, you recommend to extend read_register to read the PC, or
> "read_register is locked at the
2017 Jan 31
0
llvm.read_register for %RIP on x86_64
On 31 Jan 2017 8:58 p.m., "Kostya Serebryany" <kcc at google.com> wrote:
hmm. I am not sure I understood you. The last two paragraphs seem to
contradict each other.
So, you recommend to extend read_register to read the PC, or
"read_register is locked at the stack pointer as a design decision"?
Both. :-)
There was a design decision to only support SP because we had no