search for: structcpy

...ply while clang is emitting memcpys with pointers that may perfectly alias. If the 'mayPerfectlyAlias' flag were introduced, I could inspect that and add the noalias tag only if mayPerfectlyAlias is '0'. Note: We could also achieve the desired effect by adding a new intrinsic (llvm.structcpy?) with semantics that match the current llvm.memcpy ones (i.e. perfect-aliasing or non-aliasing, but no partial), and then reclaim llvm.memcpy for non-aliasing pointers only. I floated this idea with David Majnemer on IRC and he suggested that adding a flag to llvm.memcpy might be less disruptive a...

...s emitting memcpys with pointers that may perfectly alias. If the 'mayPerfectlyAlias' flag were introduced, I could inspect that and add the noalias tag only if mayPerfectlyAlias is '0'. >> >> Note: We could also achieve the desired effect by adding a new intrinsic (llvm.structcpy?) with semantics that match the current llvm.memcpy ones (i.e. perfect-aliasing or non-aliasing, but no partial), and then reclaim llvm.memcpy for non-aliasing pointers only. I floated this idea with David Majnemer on IRC and he suggested that adding a flag to llvm.memcpy might be less disruptive a...

...39;mayPerfectlyAlias' flag were >>>> introduced, I could inspect that and add the noalias tag only if >>>> mayPerfectlyAlias is '0'. >>>> >>>> Note: We could also achieve the desired effect by adding a new >>>> intrinsic (llvm.structcpy?) with semantics that match the current >>>> llvm.memcpy ones (i.e. perfect-aliasing or non-aliasing, but no >>>> partial), and then reclaim llvm.memcpy for non-aliasing pointers >>>> only. I floated this idea with David Majnemer on IRC and he >>>> su...

...emcpys with pointers that > may perfectly alias. If the 'mayPerfectlyAlias' flag were > introduced, I could inspect that and add the noalias tag only if > mayPerfectlyAlias is '0'. > > Note: We could also achieve the desired effect by adding a new > intrinsic (llvm.structcpy?) with semantics that match the current > llvm.memcpy ones (i.e. perfect-aliasing or non-aliasing, but no > partial), and then reclaim llvm.memcpy for non-aliasing pointers > only. I floated this idea with David Majnemer on IRC and he > suggested that adding a flag to llvm.memcpy might...

...> may perfectly alias. If the 'mayPerfectlyAlias' flag were > > introduced, I could inspect that and add the noalias tag only if > > mayPerfectlyAlias is '0'. > > > > Note: We could also achieve the desired effect by adding a new > > intrinsic (llvm.structcpy?) with semantics that match the current > > llvm.memcpy ones (i.e. perfect-aliasing or non-aliasing, but no > > partial), and then reclaim llvm.memcpy for non-aliasing pointers > > only. I floated this idea with David Majnemer on IRC and he > > suggested that adding a flag t...

.... If the 'mayPerfectlyAlias' flag were > > > introduced, I could inspect that and add the noalias tag only if > > > mayPerfectlyAlias is '0'. > > > > > > Note: We could also achieve the desired effect by adding a new > > > intrinsic (llvm.structcpy?) with semantics that match the current > > > llvm.memcpy ones (i.e. perfect-aliasing or non-aliasing, but no > > > partial), and then reclaim llvm.memcpy for non-aliasing pointers > > > only. I floated this idea with David Majnemer on IRC and he > > > suggested...