[petsc-dev] crap in next in dm.c

Matthew Knepley knepley at gmail.com
Mon Feb 16 17:02:44 CST 2015

On Mon, Feb 16, 2015 at 4:57 PM, Jed Brown <jed at jedbrown.org> wrote:

> Matthew Knepley <knepley at gmail.com> writes:
> > On Mon, Feb 16, 2015 at 4:08 PM, Satish Balay <balay at mcs.anl.gov> wrote:
> >
> >> So whats the solution [in configure?] use -Qtype-safety ?
> >>
> >
> > Can't we just not generate the extensions that say to check for types
> there?
> I don't think there is a __attribute to disable checks at the call site.

I meant if we got rid of

PETSC_EXTERN PetscErrorCode PetscSFBcastBegin(PetscSF,MPI_Datatype,const
void *rootdata,void *leafdata)
  PetscAttrMPIPointerWithType(3,2) PetscAttrMPIPointerWithType(4,2);

PetscAttrMPIPointerWithType, wouldn't it turn the check off?


What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20150216/a395e8ac/attachment.html>

More information about the petsc-dev mailing list