[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABob6iomFguOxA5ghdtDftf7GEdXUVOzSqSEd9bVVi7KB3Sg9A@mail.gmail.com>
Date: Fri, 15 Mar 2013 03:27:25 +0100
From: Lukas Odzioba <lukas.odzioba@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Feature freeze
2013/1/13 Frank Dittrich <frank_dittrich@...mail.com>:
> I'd really love to include OpenCL and CUDA version information into the
> --list=build-info output.
>
> But since I can't test it, I didn't write such a patch.
> (May be I should have considered using bull for such a test earlier.
> I am not sure when I'll have time for this.)
>
> __OPENCL_VERSION__ looks like the compile-time OpenCL version
> information, may be we can also list the run-time version if that differs.
> Probably there's also a way to check the CUDA version information.
I did some research on this topic, and after all it doesn't look so
simple as I initially though.
--list=build-info output.
Since it is build info then we should report there only what was known
at build time, not runtime - in my opinion.
Macro: __OPENCL_VERSION__ is available only during kernel compilation
and it means highest supported OCL version by THIS device.
There are also properties:
CL_DEVICE_OPENCL_C_VERSION
CL_PLATFORM_VERSION
which are available at the runtime, then I assume that we don't need them.
CL/cl.h contains:
/* OpenCL Version */
#define CL_VERSION_1_0 1
#define CL_VERSION_1_1 1
#define CL_VERSION_1_2 1
I used them to add OpenCL version to build-info output, I hope that it
is what you ment.
Patch attached,
Lukas
Download attachment "opencl_version_in_build-info_output.diff" of type "application/octet-stream" (2577 bytes)
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
