search for: planschi_test

...tor and pass a class to it that inherits from “DefinitionGenerator” right? Let’s call it “MyDefinitionGenerator" then. “MyDefinitionGenerator" needs to provide an implementation for “tryToGenerate” which contains stuff which I ignore at this point. Now I’m in step 3.) right? And oh nooo! Planschi_test is undefined. Now the tryToGenerate function is executed and I realize there, that “Planschi_test” is something coming from a different module. Normally I would call the “define” function of the DyLib I got (in the tryToGenerate function) and providing an absolute value. But I can’t because “Plans...

...ject, how do you decide that it should resolve to the definition of "test" in, for example, Planschi, as opposed to some other module? Do you just have a list of modules that you check in-order until you find a matching symbol name? You wouldn’t find a reference to “test”, you would find “Planschi_test”. We would first try resolving that with the standard C library functions. If this fails, then we will ask the object file “Planschi” if it has “test” and resolve it. If “Planschi” is not loaded for some reason, then we go on with the next symbol and mark “Planschi_test” as undefined. So… we fail l...

...ree. This is why I don’t want the LLJIT to do an automatic resolving of those symbols, because it can’t know about our structure. However, how could I achieve this then? Especially if it is not so straight forward to find the symbols that are not resolved yet. For example: Module A might reference Planschi_test Module B was loaded with name “Planschi” and has a variable called test – so our old loader would then resolve that “Planschi_test” reference with that address. However those “pathes” can get really complex like navigating to a parent and such. 1. Is there a way then, how I can lookup the addre...

Hi Lang, Thank you for your answer! This helped me again a lot!! Also that ResourceTracker is a really neat feature! Looking forward to it! :3 I changed the title cause… there is another issue I have (sorry about that…) I’m finally allowed to investigate the ORC JIT for integration into our system, which meant I got a few days to actually play around with it. However, another problem arise

Hey Lang, Thank you for your help and your patience – also for your answers in the “ORC JIT - Can modules independently managed with one LLJIT instance? + problems with ExecutionSession.lookup” mail. Both problems have the same origin so I keep writing about it here, to avoid duplication. My big problem is still handling cross references between modules with “our” name scheme. Since our old