[petsc-dev] Apparent bug with PGI on Titan with each thread calling a serial LU solve
Mark Adams
mfadams at lbl.gov
Thu May 8 08:03:22 CDT 2014
OK, sorry about that. I miss read your earlier message on this. The rest
of the code is stable so we should be able to use this branch everywhere.
Does it have the changes to KPSSetOperators, etc. ? We had some problem
with the #ifdefs not working because of this.
Thanks,
Mark
On Wed, May 7, 2014 at 7:27 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
>
> On May 7, 2014, at 9:09 PM, Mark Adams <mfadams at lbl.gov> wrote:
>
> >
> >
> >
> > On Wed, May 7, 2014 at 1:02 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
> >
> > Mark,
> >
> > Are you sure the PGI version is built with the correct branch of
> barry/make-petscoptionsobject-nonglobal ?
> >
> > In that branch line 516 of aoptions.c has case OPTION_INT:
> not a PetscFree
> >
> > Meanwhile in master line 516 has ierr =
> PetscFree(PetscOptionsObject.title);CHKERRQ(ierr);
> >
> >
> > Whoops, I was under the impression that your fixes had been merged with
> master. Did I get that wrong ... How should we proceed? I build PETSc on
> Titan for Ed so we are flexible.
>
> Unfortunately fixing PETSc master to support both thread safe and
> multiple thread within each object is complicated Ed needs to use the
> branch listed above. Hopefully this summer we’ll get the thread safety into
> Master but sadly it is not a trivial operation.
>
> Barry
>
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20140508/ffae2b43/attachment.html>
More information about the petsc-dev
mailing list