Displaying 3 results from an estimated 3 matches for "static_ctor".
2018 Jun 21
2
runStaticConstructorsDestructors() causes crash on exit
When OrcMCJITReplacement is given a new module, it asks for the module's
constructors, gives them names like $static_ctor.0, $static_ctor.1, etc.,
and saves the mangled names in a map. Later, to execute them, it uses
runViaLayer(), which looks for those symbol names in the given JIT layer.
Could one not simply execute the constructors straight away, rather than
naming them and looking them up by name later, if there i...
2018 Jun 25
2
runStaticConstructorsDestructors() causes crash on exit
...unner.cpp#L71
>
> I hope it helps.
>
> Cheers,
> Alex.
>
> > On 21. Jun 2018, at 09:27, Geoff Levner <glevner at gmail.com> wrote:
> >
> > When OrcMCJITReplacement is given a new module, it asks for the module's
> constructors, gives them names like $static_ctor.0, $static_ctor.1, etc.,
> and saves the mangled names in a map. Later, to execute them, it uses
> runViaLayer(), which looks for those symbol names in the given JIT layer.
> Could one not simply execute the constructors straight away, rather than
> naming them and looking them up by na...
2018 Jun 19
2
runStaticConstructorsDestructors() causes crash on exit
On Alex's advice I am switching from MCJIT to the Orc API to compile and
execute functions. Starting from the new clang-interpreter example in the
source code (top of the tree!), I am able to execute my functions all
right... as long as there are no constructors and destructors to call.
My question: is there a simple way, with the Orc API, to run a module's
constructors and destructors? I