[Starpu-devel] Incoherence between starpu_mpi_init and starpu_mpi_init_conf

[Philippe SWARTVAGHER <philippe.swartvagher@inria.fr>]

Hello,

We just noticed that when running Chameleon, functions 
_starpu_mpi_backend_init are not called. That came from a wrong 
detection of starpu_mpi_init_conf, and starpu_mpi_init was called 
instead. I fixed it, proposed a PR, and I am waiting for merge.

Anyway, is it normal that starpu_mpi_init() doesn't make all the staff 
of starpu_mpi_init_conf(): backend initialization and core reservation ? 
Calling starpu_init() and then starpu_mpi_init() seems to be allowed by 
the doc, but starpu_mpi_init() should also initialize backend and 
eventually reserve core IMHO.

Is it a bug ?

--
Philippe SWARTVAGHER

Doctorant
Équipe TADaaM, Inria Bordeaux Sud-Ouest