jhuber6 wrote:

> @jhuber6 Some queries (such as name and vendor) return strings, binary data 
> or arrays. This entry point allows the implementation to pre-allocate storage 
> for them.
> 
> It's also useful for offload users that want to create a generic "readInfo" 
> function that allocates and returns a void * to some memory for callers to 
> cast to the appropriate type.

I assumed those would just return a pointer to some memory the plugin manages, 
likely the assumption is that a symbol is valid only as long as its associated 
image is alive... Guess this is another case where the runtime *really* should 
be managing the memory of the image by copying it in. I really need to make 
that change.

https://github.com/llvm/llvm-project/pull/147962
_______________________________________________
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits

Reply via email to