Freddie Witherden <[email protected]> writes: > Hi Andreas, > > On 29/05/14 18:38, Andreas Kloeckner wrote: >> There's the current scheme of >> >> /home/andreas/src/pyopencl/pyopencl/__init__.py:61: CompilerWarning: >> Non-empty compiler output encountered. Set the environment variable >> PYOPENCL_COMPILER_OUTPUT=1 to see more. >> "to see more.", CompilerWarning) >> >> which is shown exactly once per program run. IIRC, I introduced this >> because the Intel CL compiler is chatty on CPUs, too. You can set that >> environment variable to control compiler chattiness. You could >> conceivably also set the environment variable programmatically. Does >> this do what you want? If not, what behavior would you like? > > I am wondering if it is possible to silence this initial output or at > least have programmatic control over it. But, more generally, would be > interested in knowing if anyone has had any success differentiating > between these spurious warnings and real warnings (say by looking for > certain keywords in the output).
Either of those sound like interesting functionality. I'd be happy to consider a patch. Andreas
pgpWO0w0H9VJN.pgp
Description: PGP signature
_______________________________________________ PyOpenCL mailing list [email protected] http://lists.tiker.net/listinfo/pyopencl
