-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all,
Recently I have been playing around with OpenCL on the Intel Xeon Phi. A quirk of the OpenCL stack (which also applies to the Intel CPU stack) is that the compiler is extremely chatty. Running a simple axpy kernel gives: /usr/local/lib/python2.7/site-packages/pyopencl/__init__.py:57: Build on <pyopencl.Device 'Intel(R) Many Integrated Core Acceleration Card' on 'Intel(R) OpenCL' at 0x1a207d8> succeeded, but said: Compilation started Compilation done Linking started Linking done Build started Kernel <sum> was successfully vectorized Done. warn(text, CompilerWarning) /usr/local/lib/python2.7/site-packages/pyopencl/__init__.py:57: CompilerWarning: From-binary build succeeded, but resulted in non-empty logs: Build on <pyopencl.Device 'Intel(R) Many Integrated Core Acceleration Card' on 'Intel(R) OpenCL' at 0x1a207d8> succeeded, but said: Linking started Linking done Build started Kernel <sum> was successfully vectorized Done. warn(text, CompilerWarning) I am not sure the best way to handle this; PyOpenCL does not appear to expose an API for programmatic control over if these 'warnings' are generated. It is of course possible to sink the output but this does not help us to decide if a genuine warning has been generated or not (which are absolutely of interest and should be displayed). How have other people handled this? Regards, Freddie. -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.20 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlOHbSEACgkQ/J9EM/uoqVfbxQCdFv/SKh3JAGGvg2jVsRSSScJs Dn8An0E4hWkjXBT2+K9gbJzePiIRX6YZ =4cPY -----END PGP SIGNATURE----- _______________________________________________ PyOpenCL mailing list [email protected] http://lists.tiker.net/listinfo/pyopencl
