search for: llvm_ptr_ty

Krzysztof Parzyszek via llvm-dev <llvm-dev at lists.llvm.org> writes: >> -----Original Message----- >> From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of David Greene >> via llvm-dev >> Sent: Thursday, August 29, 2019 10:05 AM >> To: llvm-dev <llvm-dev at lists.llvm.org> >> Subject: [EXT] [llvm-dev] Complex proposal v2 >>

On Mon, 5 Feb 2007, Dan Gohman wrote: > LLVM knows what all the types of the intrinsic functions are; I thought, > why are users (including llvm-gcc...) required to duplicate all this > information in order to use them? I mean in order to call > getOrInsertFunction to get declarations for them. That is an excellent question! :) In the bad old days, we used to allow intrinsics

...1>; def llvm_i8_ty : LLVMIntegerType<i8 , 8>; @@ -76,9 +85,10 @@ def llvm_i64_ty : LLVMIntegerType<i64, 64>; def llvm_float_ty : LLVMType<f32, "Type::FloatTyID">; def llvm_double_ty : LLVMType<f64, "Type::DoubleTyID">; -def llvm_ptr_ty : LLVMType<iPTR, "Type::PointerTyID">; // i8* -def llvm_ptrptr_ty : LLVMType<iPTR, "Type::PointerTyID">; // i8** -def llvm_descriptor_ty : LLVMType<iPTR, "Type::PointerTyID">; // global* +def llvm_ptr_ty : LLVMPointerType...

...ude/llvm/IntrinsicsPowerPC.td > =================================================================== > --- include/llvm/IntrinsicsPowerPC.td (revision 54985) > +++ include/llvm/IntrinsicsPowerPC.td (working copy) > @@ -26,6 +26,9 @@ > def int_ppc_dcbtst: Intrinsic<[llvm_void_ty, llvm_ptr_ty], [IntrWriteMem]>; > def int_ppc_dcbz : Intrinsic<[llvm_void_ty, llvm_ptr_ty], [IntrWriteMem]>; > def int_ppc_dcbzl : Intrinsic<[llvm_void_ty, llvm_ptr_ty], [IntrWriteMem]>; > + > + // sync instruction > + def int_ppc_sync : Intrinsic<[llvm_void_ty], [IntrW...

...ase is assumed (it may read and write any memory it can get access to and it may have other side effects)". But when I define the intrinsic function with different attributes, there is no difference when I dump the IR. For example, two intrinsic functions are def int_foo5 : Intrinsic<[], [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) #...

...------------- Index: include/llvm/IntrinsicsPowerPC.td =================================================================== --- include/llvm/IntrinsicsPowerPC.td (revision 54985) +++ include/llvm/IntrinsicsPowerPC.td (working copy) @@ -26,6 +26,9 @@ def int_ppc_dcbtst: Intrinsic<[llvm_void_ty, llvm_ptr_ty], [IntrWriteMem]>; def int_ppc_dcbz : Intrinsic<[llvm_void_ty, llvm_ptr_ty], [IntrWriteMem]>; def int_ppc_dcbzl : Intrinsic<[llvm_void_ty, llvm_ptr_ty], [IntrWriteMem]>; + + // sync instruction + def int_ppc_sync : Intrinsic<[llvm_void_ty], [IntrWriteMem]>; } Inde...

...ves the call" I think it needs s/return/retain/ and s/out lives/outlives/ > In addition, many APIs have changed in this release. Some of the major LLVM API changes are: The ones I encountered were: - The syntax of Intrinsics*.td changed in an incompatible way; Intrinsic<[llvm_i32_ty, llvm_ptr_ty, llvm_ptr_ty]> used to mean the return type was i32 and the parameter types were (i8*, i8*), but now it means something different (probably that the return type is {i32, i8*, i8*}, but I'm not sure). - BinaryOperator::createAnd -> CreateAnd (and similarly for lots of other createX functio...

Hello, I have a problem with pattern matching on intrinsics. I have following code in IntrinsicsX86.td: ``` let TargetPrefix = "x86" in { // All intrinsics start with "llvm.x86.". def int_x86_mpx_bndmk: Intrinsic<[llvm_x86bnd_ty], [llvm_ptr_ty, llvm_i64_ty], []>; } ``` And following instruction that is generated when @llvm.x86.mpx.bndmk is used in code: ``` let isPseudo = 1 in let usesCustomInserter = 1 in def BNDMK64rm_Int: PseudoI<(outs BNDR:$dst), (ins i64mem:$src, GR64:$shift), [(set BNDR:$dst, (int_x86_mpx_bndmk addr:$s...

LLVM knows what all the types of the intrinsic functions are; I thought, why are users (including llvm-gcc...) required to duplicate all this information in order to use them? I mean in order to call getOrInsertFunction to get declarations for them. So I wrote this patch, which allows all this code to be generated automatically. Is this a good approach? Dan -- Dan Gohman, Cray Inc. <djg at

.... Maybe some dependencies between alloca and the stackrestore instrinsic are missing or how should this work? In Intrinsics.td it says // Note: we treat stacksave/stackrestore as writemem because we don't otherwise // model their dependencies on allocas. def int_stacksave : Intrinsic<[llvm_ptr_ty]>, GCCBuiltin<"__builtin_stack_save">; def int_stackrestore : Intrinsic<[], [llvm_ptr_ty]>, GCCBuiltin<"__builtin_stack_restore">; Does "GCCBuiltin" imply "writemem", or how does the c...

...------------- Index: include/llvm/IntrinsicsPowerPC.td =================================================================== --- include/llvm/IntrinsicsPowerPC.td (revision 54985) +++ include/llvm/IntrinsicsPowerPC.td (working copy) @@ -26,6 +26,9 @@ def int_ppc_dcbtst: Intrinsic<[llvm_void_ty, llvm_ptr_ty], [IntrWriteMem]>; def int_ppc_dcbz : Intrinsic<[llvm_void_ty, llvm_ptr_ty], [IntrWriteMem]>; def int_ppc_dcbzl : Intrinsic<[llvm_void_ty, llvm_ptr_ty], [IntrWriteMem]>; + + // sync instruction + def int_ppc_sync : Intrinsic<[llvm_void_ty], [IntrWriteMem]>; } Inde...

...t; --- a/include/llvm/Intrinsics.td > +++ b/include/llvm/Intrinsics.td > @@ -344,10 +344,12 @@ def int_annotation : Intrinsic<[llvm_anyint_ty], > > //===------------------------ Trampoline Intrinsics -----------------------===// > // > -def int_init_trampoline : Intrinsic<[llvm_ptr_ty], > +def int_init_trampoline : Intrinsic<[], > [llvm_ptr_ty, llvm_ptr_ty, llvm_ptr_ty], > - [IntrReadWriteArgMem]>, > - GCCBuiltin<"__builtin_init_trampoline">; > +...

Hi! Attached set of patches splits llvm.init.trampoline into an "init" phase and an "adjust" phase, as discussed on the "Go on dragonegg" thread. Thanks! -- Sanjoy Das http://playingwithpointers.com -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Split-intrinsics-and-DAG-nodes.patch Type: text/x-diff Size: 8808 bytes Desc:

Bill, > The built-in dwarf_cfa doesn't take an argument. It returns a pointer. Ah. Sorry for confusion: gcc's __builtin_draft_cfa doesn't have any argument LLVM's eh_dwarf_cfa intrinsic has extra "offset" argument, which is i32, because we have to propagate some information from GCC to LLVM. > But there's an offset associated with the CFA. So it looks like

Hi All, Please review the 2.5 release notes here: http://llvm.org/docs/ReleaseNotes.html Let me know if you have any additions, improvements, or see any oversights. If you have commit access, please just directly change the document. The release is planned to go out in about 24 hours from now! Thanks! -Chris

...e any memory it can get access to and it may have > other side effects)". > > But when I define the intrinsic function with different attributes, > there is no difference when I dump the IR. For example, two intrinsic > functions are > > def int_foo5 : Intrinsic<[], [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: nounwi...

...read and write any memory it can get access to and it may have other side effects)". > > But when I define the intrinsic function with different attributes, there is no difference when I dump the IR. For example, two intrinsic functions are > > def int_foo5 : Intrinsic<[], [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 &...

...rite > any memory it can get access to and it may have other side effects)". > > But when I define the intrinsic function with different attributes, there > is no difference when I dump the IR. For example, two intrinsic functions > are > > def int_foo5 : Intrinsic<[], [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: nounwin...

...PowerPC.td >> =================================================================== >> --- include/llvm/IntrinsicsPowerPC.td (revision 54985) >> +++ include/llvm/IntrinsicsPowerPC.td (working copy) >> @@ -26,6 +26,9 @@ >> def int_ppc_dcbtst: Intrinsic<[llvm_void_ty, llvm_ptr_ty], >> [IntrWriteMem]>; >> def int_ppc_dcbz : Intrinsic<[llvm_void_ty, llvm_ptr_ty], >> [IntrWriteMem]>; >> def int_ppc_dcbzl : Intrinsic<[llvm_void_ty, llvm_ptr_ty], >> [IntrWriteMem]>; >> + >> + // sync instruction >> + def...

On Aug 19, 2008, at 7:18 AMPDT, Gary Benson wrote: > Hi all, > > I'm trying to implement llvm.memory.barrier on PowerPC. I've modelled > my patch (attached) on the implementation in X86, but when I try and > compile my test file (also attached) with llc I get the error "Cannot > yet select: 0x10fa4ad0: ch = MemBarrier 0x10fa4828, 0x10fa4c68, > 0x10fa4be0,