On Thu, Apr 29 2004, Gregory Wright wrote:
> It has nothing to do with shared objects.
No, it hasn't and I have never claimed that it is so.
> the main program (the one that loads the loadable modules) to explicitly
> link all of the object files that the set {, modules>}
> depends on.
No. The
Hi,
I was playing with dynamically loaded modules and had the same problem.
It has nothing to do with shared objects. What you have to do is to
force
the main program (the one that loads the loadable modules) to explicitly
link all of the object files that the set {, }
depends on.
For example, i
On Thu, Apr 29 2004, Alastair Reid wrote:
> Does passing the flag RTLD_GLOBAL to dlopen help? (man dlopen for info about
> this flag)
No, since none of the objects involved are shared objects (I use neither
dlopen or addDLL but the loadObj function). They are just compiled Haskell
modules and t
> The functions from the rts are ffi:ed into my program but when
> dynamically loading the module, these functions can't be found
> ("unknown symbol `lookupSymbol`") and neither can I load the
> HSrts.o package to make them visible due to duplicate functions
> ("I found a duplicate definition for
Hi,
by using the RTS I've made it possible to dynamically load modules for
quite some time now. However, recently I've stumbled inte quite a
problem.
I've created a bunch of modules to handle all dynamic loading for me and
things are good for simple programs. But now I want to load my dynamic
loa
Hi,
> > Results:
> >
> >method runtime (s)
> >---
> >pure0.7
> >ffi 3.2
> >fastMut 15
> >ioref 23
>
> I very strongly suspect that it is the unsafePerformIO that hurts
> performance in the fastMut
