Drop fpga_funcs_name field, we do not actually need it for FPGA

doc/doxygen/440_fpga_support.doxy

@@ -31,15 +31,14 @@ possibility of having heterogeneous accelerators and processors to interact on t
 
 \section PortingApplicationsToFPGA Porting Applications To FPGA
 
-The simplest way to port an application to FPGA is to set the field
-starpu_codelet::fpga_funcs_name, to provide StarPU with the function
-name of the FPGA implementation, so for instance:
+The way to port an application to FPGA is to set the field
+starpu_codelet::fpga_funcs, to provide StarPU with the function
+for FPGA implementation, so for instance:
 
 \verbatim
 struct starpu_codelet cl =
 {
     .fpga_funcs = {myfunc},
-    .fpga_funcs_name = {"myfunc"},
     .nbuffers = 1,
 }
 \endverbatim

doc/doxygen/chapters/440_fpga_support.doxy

@@ -30,14 +30,14 @@ The Simple Live CPU interface (SLiC) is Maxeler’s application programming inte
 
 \section PortingApplicationsToFPGA Porting Applications to FPGA
 
-The simplest way to port an application to FPGA is to set the field starpu_codelet::fpga_funcs_name, to provide StarPU with the function
-name of the FPGA implementation, so for instance:
+The way to port an application to FPGA is to set the field
+starpu_codelet::fpga_funcs, to provide StarPU with the function
+for FPGA implementation, so for instance:
 
 \verbatim
 struct starpu_codelet cl =
 {
     .fpga_funcs = {myfunc},
-    .fpga_funcs_name = {"myfunc"},
     .nbuffers = 1,
 }
 \endverbatim
@@ -167,7 +167,6 @@ void fpga_add(void *buffers[], void *cl_arg)
     .cpu_funcs = {cpu_func},
     .cpu_funcs_name = {"cpu_func"},
     .fpga_funcs = {fpga_add},
-    .fpga_funcs_name={"fpga_add"},
     .nbuffers = 3,
     .modes = {STARPU_R, STARPU_R, STARPU_W}
   };

include/starpu_task.h

@@ -461,16 +461,6 @@ struct starpu_codelet
 	*/
 	const char *cpu_funcs_name[STARPU_MAXIMPLEMENTATIONS];
 
-	/**
-           Optional array of strings which provide the name of the FPGA
-           functions referenced in the array
-           starpu_codelet::fpga_funcs. This can be used when running on
-           MIC devices for StarPU to simply look
-           up the MIC function implementation through its name.
-        */
-
-	char *fpga_funcs_name[STARPU_MAXIMPLEMENTATIONS];
-
 	/** 
 	 fpga kernel type
         */

tests/perfmodels/max_fpga.c

@@ -68,7 +68,6 @@ static struct starpu_codelet cl =
     .cpu_funcs_name = {"cpu_func"},
 //#ifdef STARPU_USE_FPGA
     .fpga_funcs = {fpga_mult},
-    .fpga_funcs_name={"fpga_mult"},
 //#endif
     .nbuffers = 3,
     .modes = {STARPU_R, STARPU_R, STARPU_W}