On 10 March 2017 at 03:19, Barry Smith <[email protected]> wrote: > PetscMallocRegister(malloc,realloc,free,&basicmalloc); > PetscMallocRegister(PetscMallocDebug,PetscReallocDebug, > PetscFreeDebug,&debugmalloc); > PetscMallocRegister(PetscMallocHBW,PetscReallocHBW,PetscFreeHBW,& > hbwmalloc); >
I'm wondering whether we should also handle calloc() here, and implement PetscCalloc properly. As I understand it, calloc != malloc+memset, and the differences might be important in multicore+multithreading scenarios and the first-touch policy. -- Lisandro Dalcin ============ Research Scientist Computer, Electrical and Mathematical Sciences & Engineering (CEMSE) Extreme Computing Research Center (ECRC) King Abdullah University of Science and Technology (KAUST) http://ecrc.kaust.edu.sa/ 4700 King Abdullah University of Science and Technology al-Khawarizmi Bldg (Bldg 1), Office # 0109 Thuwal 23955-6900, Kingdom of Saudi Arabia http://www.kaust.edu.sa Office Phone: +966 12 808-0459
