search for: notifyobjectpreload

...at this is really two options, in that the code to separate out the per-function EH frame contribution could go in either the client memory manager or in the loader.) 2. Add a notification similar to NotifyObjectEmitted, but which runs just before the call to Dyld.loadObject. Something like NotifyObjectPreLoaded. The LLILC-specific MemoryManager could use this hook to scan the object::ObjectFile and pass whatever it needs to the CoreCLR. This seems like a decent option to me, but I don't know if it would be considered a bad loss of encapsulation to passs out the object::ObjectFile in the state wher...

...at this is really two options, in that the code to separate out the per-function EH frame contribution could go in either the client memory manager or in the loader.) 2. Add a notification similar to NotifyObjectEmitted, but which runs just before the call to Dyld.loadObject. Something like NotifyObjectPreLoaded. The LLILC-specific MemoryManager could use this hook to scan the object::ObjectFile and pass whatever it needs to the CoreCLR. This seems like a decent option to me, but I don't know if it would be considered a bad loss of encapsulation to passs out the object::ObjectFile in the state wher...

...> in that the code to separate out the per-function EH frame contribution > could go in either the client memory manager or in the loader.) > > 2. Add a notification similar to NotifyObjectEmitted, but which > runs just *before* the call to Dyld.loadObject. Something like > NotifyObjectPreLoaded. The LLILC-specific MemoryManager could use this > hook to scan the object::ObjectFile and pass whatever it needs to the > CoreCLR. This seems like a decent option to me, but I don't know if it > would be considered a bad loss of encapsulation to passs out the > object::ObjectFi...

...at this is really two options, in that the code to separate out the per-function EH frame contribution could go in either the client memory manager or in the loader.) 2. Add a notification similar to NotifyObjectEmitted, but which runs just before the call to Dyld.loadObject. Something like NotifyObjectPreLoaded. The LLILC-specific MemoryManager could use this hook to scan the object::ObjectFile and pass whatever it needs to the CoreCLR. This seems like a decent option to me, but I don't know if it would be considered a bad loss of encapsulation to passs out the object::ObjectFile in the state wher...

...at this is really two options, in that the code to separate out the per-function EH frame contribution could go in either the client memory manager or in the loader.) 2. Add a notification similar to NotifyObjectEmitted, but which runs just before the call to Dyld.loadObject. Something like NotifyObjectPreLoaded. The LLILC-specific MemoryManager could use this hook to scan the object::ObjectFile and pass whatever it needs to the CoreCLR. This seems like a decent option to me, but I don't know if it would be considered a bad loss of encapsulation to passs out the object::ObjectFile in the state wher...

...at this is really two options, in that the code to separate out the per-function EH frame contribution could go in either the client memory manager or in the loader.) 2. Add a notification similar to NotifyObjectEmitted, but which runs just before the call to Dyld.loadObject. Something like NotifyObjectPreLoaded. The LLILC-specific MemoryManager could use this hook to scan the object::ObjectFile and pass whatever it needs to the CoreCLR. This seems like a decent option to me, but I don't know if it would be considered a bad loss of encapsulation to passs out the object::ObjectFile in the state wher...