search for: intrargmemon

On 01/11, Daniel Berlin via llvm-dev wrote: > > > > def int_experimental_directive : Intrinsic<[], [llvm_metadata_ty], > > [IntrArgMemOnly], > > "llvm.experimental.directive">; > > > > def int_experimental_dir_qual : Intrinsic<[], [llvm_metadata_ty], > > [IntrArgMemOnly], > > "llvm.experimental.dir.qual">; > > > > def int_experimental_dir_qual_opnd : Intrinsic&lt...

...o by transformation passes (e.g. automated parallelization). The names used here are similar to those used by our internal prototype, but obviously we expect a community bikeshed discussion. def int_experimental_directive : Intrinsic<[], [llvm_metadata_ty], [IntrArgMemOnly], "llvm.experimental.directive">; def int_experimental_dir_qual : Intrinsic<[], [llvm_metadata_ty], [IntrArgMemOnly], "llvm.experimental.dir.qual">; def int_experimental_dir_qual_opnd : Intrinsic<[], [llvm_metadata_ty, llvm_any_ty], [IntrArgMemOnly], "llvm.e...

...lso by transformation passes (e.g. automated parallelization). The names used here are similar to those used by our internal prototype, but obviously we expect a community bikeshed discussion. def int_experimental_directive : Intrinsic<[], [llvm_metadata_ty], [IntrArgMemOnly], "llvm.experimental.directive">; def int_experimental_dir_qual : Intrinsic<[], [llvm_metadata_ty], [IntrArgMemOnly], "llvm.experimental.dir.qual">; def int_experimental_dir_qual_opnd : Intrinsic<[], [llvm_metadata_ty, llvm_any_ty], [IntrArgMemOnly], "llvm.e...

...ization). The names used here are similar to those used >> by >> our internal prototype, but obviously we expect a community bikeshed >> discussion. >> >> def int_experimental_directive : Intrinsic<[], [llvm_metadata_ty], >> [IntrArgMemOnly], >> "llvm.experimental.directive">; >> >> def int_experimental_dir_qual : Intrinsic<[], [llvm_metadata_ty], >> [IntrArgMemOnly], >> "llvm.experimental.dir.qual">; >> >> def int_experimental_dir_qual_opnd : Intrinsic<[], &g...

...lso by transformation passes (e.g. automated parallelization). The names used here are similar to those used by our internal prototype, but obviously we expect a community bikeshed discussion. def int_experimental_directive : Intrinsic<[], [llvm_metadata_ty], [IntrArgMemOnly], "llvm.experimental.directive">; def int_experimental_dir_qual : Intrinsic<[], [llvm_metadata_ty], [IntrArgMemOnly], "llvm.experimental.dir.qual">; def int_experimental_dir_qual_opnd : Intrinsic<[], [llvm_metadata_ty, llvm_any_ty], [IntrArgMemOnly], "llvm.e...

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 >>

....g. > automated parallelization). The names used here are similar to those > used by our internal prototype, but obviously we expect a community > bikeshed discussion. > > def int_experimental_directive : Intrinsic<[], [llvm_metadata_ty], > [IntrArgMemOnly], > "llvm.experimental.directive">; > > def int_experimental_dir_qual : Intrinsic<[], [llvm_metadata_ty], > [IntrArgMemOnly], "llvm.experimental.dir.qual">; > > def int_experimental_dir_qual_opnd : Intrinsic<[], [llvm_metadata_ty, > llvm_a...

...gt; automated parallelization). The names used here are similar to those > used by > our internal prototype, but obviously we expect a community bikeshed > discussion. > > def int_experimental_directive : Intrinsic<[], [llvm_metadata_ty], > [IntrArgMemOnly], > "llvm.experimental.directive">; > > def int_experimental_dir_qual : Intrinsic<[], [llvm_metadata_ty], > [IntrArgMemOnly], > "llvm.experimental.dir.qual">; > > def int_experimental_dir_qual_opnd : Intrinsic<[], > [llvm_metadata_ty, llvm...

...lso by transformation passes (e.g. automated parallelization). The names used here are similar to those used by our internal prototype, but obviously we expect a community bikeshed discussion. def int_experimental_directive : Intrinsic<[], [llvm_metadata_ty], [IntrArgMemOnly], "llvm.experimental.directive">; def int_experimental_dir_qual : Intrinsic<[], [llvm_metadata_ty], [IntrArgMemOnly], "llvm.experimental.dir.qual">; def int_experimental_dir_qual_opnd : Intrinsic<[], [llvm_metadata_ty, llvm_any_ty], [IntrArgMemOnly], "llvm.e...

...lso by transformation passes (e.g. automated parallelization). The names used here are similar to those used by our internal prototype, but obviously we expect a community bikeshed discussion. def int_experimental_directive : Intrinsic<[], [llvm_metadata_ty], [IntrArgMemOnly], "llvm.experimental.directive">; def int_experimental_dir_qual : Intrinsic<[], [llvm_metadata_ty], [IntrArgMemOnly], "llvm.experimental.dir.qual">; def int_experimental_dir_qual_opnd : Intrinsic<[], [llvm_metadata_ty, llvm_any_ty], [IntrArgMemOnly], "llvm.e...

...now see more clearly how things work with these properties. However, what would be an object whose address is potentially known by a callee? I suppose the intrinsic arguments and global variable? So IIUC, if not restricted by *only properties, an intrinsic could access to: - only its arguments if IntrArgMemOnly specified, - its arguments and the global variable as well if Intr*Mem (other than IntrNoMem) specified. Please tell me if I'm correct or not! Thanks again, On Wed, Jul 24, 2019, 17:27 Doerfert, Johannes <jdoerfert at anl.gov> wrote: > Hi Son Tuan Vu, > > if not restricte...

...properties. However, what would be an object whose address is potentially > > known by a callee? I suppose the intrinsic arguments and global variable? > > > > So IIUC, if not restricted by *only properties, an intrinsic could access > > to: > > - only its arguments if IntrArgMemOnly specified, > > - its arguments and the global variable as well if Intr*Mem (other than > > IntrNoMem) specified. > > > > Please tell me if I'm correct or not! > > > > Thanks again, > > > > > > > > On Wed, Jul 24, 2019, 17:27 Doerfert...

...t both to be removed, since the intrinsic is now also a dead store. - IntrReadMem: memset() and the intrinsic are both optimized away *unexpectedly* (CSE removes the intrinsic, then InstCombine removes memset). The latter is understandable, but why the intrinsic gets optimized in the first place? - IntrArgMemOnly: none gets optimized away as expected - ReadOnly<0>: none gets optimized away as expected - ReadNone<0> / WriteOnly<0>: none gets optimized *unexpectedly* Am I missing something here or there are indeed bugs here? Btw, can you tell me how and why 'tail' changes the opti...

Hello, According to include/llvm/IR/Intrinsics.td, InstrReadMem property indicates that the intrinsic only reads from and does not write to memory. Does this mean that it can read anywhere in the memory? Because we already have 'InstrArgMemOnly' for intrinsics which only access memory that its argument(s) point(s) to. If 'InstrReadMem' really means read from anywhere in the

...ILTIN(__builtin_dummy, "v?", "n") > in tools/clang/include/clang/Basic/BuiltinsX86.def > > Also, what should be the type passed in include/llvm/IR/IntrinsicsX86.td > def dummy : GCCBuiltin<"__builtin_dummy">, > Intrinsic<[], [llvm_???_ty], [IntrArgMemOnly] /* , "llvm.dummy" */>; > > > Thanks, > Dounia > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.llvm.org/pipermail/llvm-dev/ > attachments/20171204/b89dafd0/attachment-0001.html> > > --------------...