search for: llvmorclljitaddobjectfil

...rther in the BoF) is: For object files: - For raw OrcV2 components you'll want to create an RTDyldObjectLinkingLayer or ObjectLinkingLayer and use the 'add' method. - For an LLJIT instance you can just call the 'addObjectFile' method. - For the OrcV2 C API you can call the 'LLVMOrcLLJITAddObjectFile' function. For static libraries: - For raw OrcV2 components or an LLJIT instance you can attach a StaticLibraryDefinitionGenerator [1] to the JITDylib that you would like to load the library into. See [2] for an example. - For the OrcV2 C API we will just need to add a method to wrap the oper...

...iles: > > - For raw OrcV2 components you'll want to create an > RTDyldObjectLinkingLayer or ObjectLinkingLayer and use the 'add' method. > > - For an LLJIT instance you can just call the 'addObjectFile' method. > > - For the OrcV2 C API you can call the 'LLVMOrcLLJITAddObjectFile' > function. > > > > For static libraries: > > - For raw OrcV2 components or an LLJIT instance you can attach a > StaticLibraryDefinitionGenerator [1] to the JITDylib that you would like to > load the library into. See [2] for an example. > > - For the OrcV2 C...

...w OrcV2 components you'll want to create an >>> RTDyldObjectLinkingLayer or ObjectLinkingLayer and use the 'add' method. >>> > - For an LLJIT instance you can just call the 'addObjectFile' method. >>> > - For the OrcV2 C API you can call the 'LLVMOrcLLJITAddObjectFile' >>> function. >>> > >>> > For static libraries: >>> > - For raw OrcV2 components or an LLJIT instance you can attach a >>> StaticLibraryDefinitionGenerator [1] to the JITDylib that you would like to >>> load the library into. See...

...ghly right? > > Independent questions about the current C API: > - Would be nice to document [non-]mangling behaviour of > LLVMOrcLLJITLookup() > - Do I understand correctly that there's no way to keep a memory buffer > with an object file alive after adding it with > LLVMOrcLLJITAddObjectFile()? But that it's fine to create multiple > buffers for the same memory with LLVMCreateMemoryBufferWithMemoryRange()? > > > > You can call ResourceTracker::remove at any time to remove all symbols > and > > resources associated with a tracker. Any active compiles assoc...

Hi Andres, A topic that I'd find interesting is what it'd take to make it easier to > use profile guided optimization in the context of JIT. A few years back > I crudely hacked this together, but it was fairly ugly. It'd be nice to > make that easier. Possibly too complicated for that type of session? We couldn't go into detail, but we could kick off a discussion and

Hi All, I've updated the orcv1 removal branch ( https://github.com/lhames/llvm-project/tree/orcv1-removal) with an initial patch for removable code. If anyone wants to follow along with the development or share thoughts on the design you're very welcome to. I'll be adding tests and comments this week, but for anyone who wants to take an early look the main elements are defined in