Am Sun, 5 Oct 2014 11:40:13 +0200
"O. Hartmann" <[email protected]> schrieb:

> Am Sun, 05 Oct 2014 11:21:23 +0200
> Vincent Danjean <[email protected]> schrieb:
> 
> > On 05/10/2014 10:17, Vincent Danjean wrote:
> > > On 05/10/2014 09:42, Pekka Jääskeläinen wrote:
> > >> On 10/04/2014 08:52 PM, O. Hartmann wrote:
> > >>> ^ ; /usr/local/include/ocl_icd.h:930:11: error: unknown type name
> > >>> 'cl_pipe_properties'; did you mean 'cl_context_properties'? const
> > >>> cl_pipe_properties * /* properties */, ^~~~~~~~~~~~~~~~~~ 
> > >>> cl_context_properties
> > >>
> > >> This is an ocl_icd.h issue. It refers to OpenCL 2.0 types while you 
> > >> probably
> > >> have 1.1 or 1.2 cl.h.
> > > 
> > > Indeed, ocl-icd added support for OpenCL 2.0 since the 2.2.0 release.
> > [...]
> > > PS: in fact, perhaps entries must simply by garded by CL_VERSION_X_Y
> > > macro, so that ocl_icd.h adapt itself to OpenCL headers used at build 
> > > time.
> > 
> > I just implemented that and releases 2.2.2. Please, check if this correctly
> > fix your problem.
> > 
> 
> I have installed ocl-icd-2.2.2.
> 
> POCL bails out now at this error:
> 
> [...]
> gmake[7]: Entering directory
> `/usr/ports/devel/pocl/work/pocl-0.10/lib/CL/devices/topology' /bin/sh 
> ../../../../libtool
> --tag=CC   --mode=compile clang35 -DHAVE_CONFIG_H -I. -I../../../..
> -I../../../../fix-include -I../../../../include -I../../../../lib/CL/devices
> -I../../../../lib/CL -I/usr/local/include/libxml2 -I/usr/local/include
> -I/usr/local/include   -I/usr/local/llvm35/include -I/usr/local/include  -O2 
> -pipe -O3
> -march=native  -pthread -fstack-protector -fno-strict-aliasing -MT
> libpocl_devices_topology_la-pocl_topology.lo -MD -MP
> -MF .deps/libpocl_devices_topology_la-pocl_topology.Tpo -c -o
> libpocl_devices_topology_la-pocl_topology.lo `test -f 'pocl_topology.c' || 
> echo
> './'`pocl_topology.c libtool: compile:  clang35 -DHAVE_CONFIG_H -I. 
> -I../../../..
> -I../../../../fix-include -I../../../../include -I../../../../lib/CL/devices
> -I../../../../lib/CL -I/usr/local/include/libxml2 -I/usr/local/include
> -I/usr/local/include -I/usr/local/llvm35/include -I/usr/local/include -O2 
> -pipe -O3
> -march=native -pthread -fstack-protector -fno-strict-aliasing -MT
> libpocl_devices_topology_la-pocl_topology.lo -MD -MP
> -MF .deps/libpocl_devices_topology_la-pocl_topology.Tpo -c pocl_topology.c  
> -fPIC -DPIC
> -o .libs/libpocl_devices_topology_la-pocl_topology.o 
> 
> In file included from pocl_topology.c:24:
> In file included from ../../../../lib/CL/pocl_cl.h:36:
> In file included from ../../../../lib/CL/pocl_icd.h:39:
> /usr/local/include/ocl_icd.h:33:34: warning: unknown warning group '-Wcpp', 
> ignored
> [-Wunknown-pragmas] #  pragma GCC diagnostic ignored "-Wcpp"
>                                  ^
> /usr/local/include/ocl_icd.h:1473:37: error: duplicate member 'clUnknown136'
>   CL_API_ENTRY cl_int (CL_API_CALL* clUnknown136)(
>                                     ^
> /usr/local/include/ocl_icd.h:1470:37: note: previous declaration is here
>   CL_API_ENTRY cl_int (CL_API_CALL* clUnknown136)(void);
> 
> 
> 
> Regards,
> Oliver

Looking into the header /usr/local/include/ocl_icd.h, there are two times the
declaration of  CL_API_ENTRY cl_int (CL_API_CALL* clUnknown136):


[...] Line 1462:
#ifdef CL_VERSION_2_0
  CL_API_ENTRY cl_int (CL_API_CALL*clSetKernelExecInfo)(
    cl_kernel            /* kernel */,
    cl_kernel_exec_info  /* param_name */,
    size_t               /* param_value_size */,
    const void *         /* param_value */
  ) CL_API_SUFFIX__VERSION_2_0;
#else
  CL_API_ENTRY cl_int (CL_API_CALL* clUnknown136)(void);
#endif

  CL_API_ENTRY cl_int (CL_API_CALL* clUnknown136)(
    void);
[...]

If CL_VERSION_2_0 isn't set - as it seems the case in POCL-0.10, then there is 
two times
the declaration of CL_API_ENTRY cl_int (CL_API_CALL* clUnknown136)(void);, 
right?

And this seems to me as a bug.

Regards,
Oliver

Attachment: signature.asc
Description: PGP signature

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
pocl-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pocl-devel

Reply via email to