Sorry if this has been discussed already...
I am trying to understand whether there is an underlying reason why llvm::CloneModule takes argument function ShouldCloneDefinition to discriminate on objects being cloned, but blindly copies all named metadata...?
In my case this results in debug nodes that are creating uses/relocations for global objects that were _not_ copied per ShouldCloneDefinition...
Before I jump head on into unfamiliar code, I would like to understand why this wheel was not invented in the first place
Thanks.
Sergei Larin
P.S. Also, if this does need fixing, please suggest the proper strategy for it... Thanks.