Reviewed-by: Eduardo Lima Mitev <el...@igalia.com> On 04/29/2016 05:39 PM, Emil Velikov wrote: > Ping ? > Considering to trivial this is I'm inclined to push it later on today. > > On 21 April 2016 at 13:20, Emil Velikov <emil.l.veli...@gmail.com> wrote: >> From: Emil Velikov <emil.veli...@collabora.com> >> >> The macro has been gone since commit 1f1cf6fcb0e "anv: Get rid of >> GENX_FUNC" >> >> Signed-off-by: Emil Velikov <emil.veli...@collabora.com> >> --- >> src/intel/genxml/gen_macros.h | 14 -------------- >> 1 file changed, 14 deletions(-) >> >> diff --git a/src/intel/genxml/gen_macros.h b/src/intel/genxml/gen_macros.h >> index 052c57f..868bc22 100644 >> --- a/src/intel/genxml/gen_macros.h >> +++ b/src/intel/genxml/gen_macros.h >> @@ -28,20 +28,6 @@ >> * The prefixing macros GENX() and genX() automatically prefix whatever you >> * give them by GENX_ or genX_ where X is the gen number. >> * >> - * You can declare a function to be used on some range of gens like this: >> - * >> - * GENX_FUNC(GEN7, GEN75) void >> - * genX(my_function_name)(args...) >> - * { >> - * // Do stuff >> - * } >> - * >> - * If the file is compiled for any set of gens containing gen7 and gen75, >> - * the function will effectively only get compiled twice as >> - * gen7_my_function_nmae and gen75_my_function_name. The function has to >> - * be compilable on all gens, but it will become a static inline that gets >> - * discarded by the compiler on all gens not in range. >> - * >> * You can do pseudo-runtime checks in your function such as >> * >> * if (GEN_GEN > 8 || GEN_IS_HASWELL) { >> -- >> 2.8.0 >> > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev >
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev