← Back to team overview

dolfin team mailing list archive

Re: JIT compiling in Dolfin

 

On Thu, 2010-05-27 at 18:52 -0700, Johan Hake wrote:
> You can controll this by setting the environment variable:
> 
>   INSTANT_CACHE_DIR
> 
> to different directories for the different DOLFIN builds.
> 
> If you use different conf files for the different DOLFIN builds you can easily 
> controll the instant cache dir from within these.
> 
> We once included the dolfin version in the cache id, but it was removed as it 
> the ufc python module is not dependent on anything in dolfin. Not sure how 
> true this is in reality though.
> 
> What kind of troubles have you encountered?
> 
> Johan
> 

The shared library in the cache is linked against another Dolfin and
therefore it wouldn't load. 

I've actually never experienced this, but Kristian showed it to me
yesterday. We could of course do 'instant-clean' to get it working, 
but the problem was that Dolfin/Instant did not distinguish between 
the different Dolfin variants which was actually of the same version. 

Kent

> 
> On Thursday May 27 2010 14:55:53 Kent Andre wrote:
> > Hi, just realized that (thanks to Kristian V-S) that there is a problem
> > with the jit compiling in Dolfin / Instant. If you have several Dolfin
> > instances compiled in different ways you may run into trouble as the
> > caching mechanism does not recognize the differences. Either Instant
> > should include compiling options in the checksum or Dolfin should
> > uniquely represent itself with an "id". Opinions ?
> > 
> > Kent
> > 
> > 
> > _______________________________________________
> > Mailing list: https://launchpad.net/~dolfin
> > Post to     : dolfin@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~dolfin
> > More help   : https://help.launchpad.net/ListHelp





Follow ups

References