search for: parallel_protected

...mory accesses (the reg2mem example.) I'm wondering if perhaps we can make the metadata more user-friendly by providing a single loop metadata which can be expanded into "safer" metadata as required. Specifically a loop pass could be added that expands llvm.loop.parallel into llvm.loop.parallel_protected + llvm.mem.parallel_loop_access. Perhaps there are simpler options I've overlooked? paul

...eg2mem example.) I'm wondering if perhaps we > can make the metadata more user-friendly by providing a single loop metadata > which can be expanded into "safer" metadata as required. Specifically a loop > pass could be added that expands llvm.loop.parallel into > llvm.loop.parallel_protected + llvm.mem.parallel_loop_access. Did I understand this correctly: llvm.loop.parallel would become a version which does not require the parallel_loop_access? Basically it would be a placeholder for a later pass (before unsafe optimizations?) that converts it to the "safe" metadata pair? T...

...I'm >> wondering if perhaps we can make the metadata more user-friendly by >> providing a single loop metadata which can be expanded into "safer" >> metadata as required. Specifically a loop pass could be added that >> expands llvm.loop.parallel into llvm.loop.parallel_protected + >> llvm.mem.parallel_loop_access. >> >> Perhaps there are simpler options I've overlooked? >> >> paul >> >> >> >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.u...

...adata more user-friendly >>>> by >>>> providing a single loop metadata which can be expanded into >>>> "safer" >>>> metadata as required. Specifically a loop pass could be added that >>>> expands llvm.loop.parallel into llvm.loop.parallel_protected + >>>> llvm.mem.parallel_loop_access. >>>> >>>> Perhaps there are simpler options I've overlooked? >>>> >>>> paul >>>> >>>> >>>> >>>> >>>> ______________________________...

...an make the metadata more user-friendly > >> by > >> providing a single loop metadata which can be expanded into > >> "safer" > >> metadata as required. Specifically a loop pass could be added that > >> expands llvm.loop.parallel into llvm.loop.parallel_protected + > >> llvm.mem.parallel_loop_access. > >> > >> Perhaps there are simpler options I've overlooked? > >> > >> paul > >> > >> > >> > >> > >> _______________________________________________ > >&gt...

...eg2mem example.) I'm > wondering if perhaps we can make the metadata more user-friendly by > providing a single loop metadata which can be expanded into "safer" > metadata as required. Specifically a loop pass could be added that > expands llvm.loop.parallel into llvm.loop.parallel_protected + > llvm.mem.parallel_loop_access. > > Perhaps there are simpler options I've overlooked? > > paul > > > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > htt...

...by > >>>> providing a single loop metadata which can be expanded into > >>>> "safer" > >>>> metadata as required. Specifically a loop pass could be added > >>>> that > >>>> expands llvm.loop.parallel into llvm.loop.parallel_protected + > >>>> llvm.mem.parallel_loop_access. > >>>> > >>>> Perhaps there are simpler options I've overlooked? > >>>> > >>>> paul > >>>> > >>>> > >>>> > >>>> &g...

...> providing a single loop metadata which can be expanded into > > >>>> "safer" > > >>>> metadata as required. Specifically a loop pass could be added > > >>>> that > > >>>> expands llvm.loop.parallel into llvm.loop.parallel_protected + > > >>>> llvm.mem.parallel_loop_access. > > >>>> > > >>>> Perhaps there are simpler options I've overlooked? > > >>>> > > >>>> paul > > >>>> > > >>>> > > &gt...

...I'm wondering if perhaps we >> can make the metadata more user-friendly by providing a single loop metadata >> which can be expanded into "safer" metadata as required. Specifically a loop >> pass could be added that expands llvm.loop.parallel into >> llvm.loop.parallel_protected + llvm.mem.parallel_loop_access. > > Did I understand this correctly: llvm.loop.parallel would become > a version which does not require the parallel_loop_access? Basically it > would be a placeholder for a later pass (before unsafe optimizations?) that > converts it to the "sa...

...viding a single loop metadata which can be expanded into >>>>>>> "safer" >>>>>>> metadata as required. Specifically a loop pass could be added >>>>>>> that >>>>>>> expands llvm.loop.parallel into llvm.loop.parallel_protected + >>>>>>> llvm.mem.parallel_loop_access. >>>>>>> >>>>>>> Perhaps there are simpler options I've overlooked? >>>>>>> >>>>>>> paul >>>>>>> >>>>>>>...