search for: parallel_under_construction

...metadata" would be merely book keeping until the final IR is generated in Clang (with the safe metadata). Maybe some other book keeping mechanism could do? If it's not easily workable (I'm not a Clang expert) then I'd propose a descriptive name for the new metadata like llvm.loop.parallel_under_construction that strongly states that it's for this purpose only and should not be used for anything during optimizations (as it's not safe to do so!). -- --Pekka

Hi, I've been working on clang codegen for #pragma ivdep and creating the llvm.mem.parallel_loop_access metadata seems quite difficult. The main problem is that there are so many places where loads and stores are created and all of them need to be changed when emitting a parallel loop. Note that creating llvm.loop.parallel is not a problem. One option is to modify IRBuilder to enable

...; would be merely book keeping until the final IR is > generated in Clang (with the safe metadata). Maybe some other book keeping > mechanism could do? If it's not easily workable (I'm not a Clang expert) > then I'd propose a descriptive name for the new metadata like llvm.loop.parallel_under_construction that strongly states that > it's for this purpose only and should not be used for anything > during optimizations (as it's not safe to do so!). > Those are fair points and I can't say whether or not there are other potential users. Certainly clang could use custom loop metada...