search for: setgc

This is also happening when using the C++ APIs. It looks like an MCJIT and SetGC interaction. I'm lost on how to proceed further. On Tue, Mar 31, 2015 at 10:42 PM, Hayden Livingston <halivingston at gmail.com> wrote: > The erlang was a typo, I was trying things out. > > I've updated the bug with a C program, which exhibits the problem. > > To ans...

...the generated IR. If you manually create the expected IR and run it through opt/llc, does that work? Can you include the full output of this example? Both the IR and the error would be useful to see. One observation, it looks like you're using the erlang GC not shadow stack? e.g. LLVM.SetGC(sum, "erlang"); Philip -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150331/d683ff0d/attachment.html>

..... it will be treated in special way by the code generator? If I set my GC to Shadowstack and mark all object pointers as GCroots, will this be 100% correct? Or do I need to myself in my code gen phase spill registers? Or does ShadowStack essentially do that for me? I guess my question here is F.SetGC("shadow-stack") + gcroot is enough for a precise GC or do I need to do more work in my frontend to do things so that processor register stored pointers are identified. HA -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/l...

...ourse, it doesn't even exist at runtime. Specifically, the renames are: Collector -> GCStrategy CollectorMetadata -> GCFunctionInfo CollectorModuleMetadata -> GCModuleInfo CollectorRegistry -> GCRegistry Function::getCollector -> getGC [setGC, hasGC, clearGC] Several accessors and nested types have also been renamed to be consistent. These changes should be obvious. Please let me know if you have any questions! Thanks, Gordon P.S. Sorry for the short notice; this just came up yesterday. -------------- next part -------------- A...

Hi, I've followed the LLVM tutorial<http://llvm.org/docs/tutorial/LangImpl4.html> to create an execution environment for my DSL and want to enable the shadow stack for garbage collection. On all functions generated by my compiler I call setGC("shadow-stack"). I end up with IR functions like this: define float @"main float"(float %x) gc "shadow-stack" { entry: ...... ...... } When I try to execute a function using executionEngine->getPointerToFunction(myFunction) it returns the following error: unsuppo...

...se let me know! Near Term Changes: - Migrate ownership of GCStrategy objects from GCModuleInfo to LLVMContext. In theory, this looses the ability for two different Modules to have the same collector with different state, but I know of no use case for this. - Modify the primary Function::getGC/setGC interface to return a reference the GCStrategy object, not a string. I will provide a Function::setGCString and getGCString. - Extend the GCStrategy class to include a notion of which compilation strategy is being used. The two choices right now will be Legacy and Statepoint. (Longer term, t...

Thanks, Philip. I have a sinking feeling it's not your change, but could you share the commit and so I can try it out locally? Bug: https://llvm.org/bugs/show_bug.cgi?id=23095 The reason I think it is not your change is because I tried a shared library build of LLVM 3.5.1 and that also failed with this error. Maybe it is because I'm using a package that makes an LLVM DLL for Windows.

On Tue, Apr 4, 2017 at 12:36 PM, Duncan P. N. Exon Smith < dexonsmith at apple.com> wrote: > > On 2017-Apr-04, at 12:12, Peter Collingbourne <peter at pcc.me.uk> wrote: > > On Mon, Apr 3, 2017 at 8:13 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > >> >> On Apr 3, 2017, at 7:08 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: >>