gat3way

What I meant is that with cryptohaze's approach (which hashkill previously followed btw), the binary is either dynamically linked to libOpenCL, or not (depends on build-time specifics). A binary that...

I am going to close this (now specifying --disable-amd-ocl at configure-time should solve the issue) - still the root cause is unknown though

Ooops, sorry, should have re-read that thread before closing, looks like 10 days are enough to forget what it was really about :( Reopening it. I am now writing a...

OK, that's the response from PaX developers: # ...i think the problem you ran into is this: http://forums.grsecurity.net/viewtopic.php?f=3&t=2194 if the 'bad' library in question doesn't do runtime codegen and just...

ZeroChaos, do you experience the same problem with any other OpenCL software? Also, does execstack -c /usr/lib/libOpenCL.so fix the issue for you? If that's the case then we should perhaps...

Well it depends on the nvidia opencl stack present in order to build the kernels (compilation calls clBuildProgram()). Without it, it would refuse to build them. Then the question is...

In the ideal case yes. However, both nvidia and amd stack require that the hardware is present. In the AMD case we can cross-compile for hardware that is not available,...

Yes and no - it is a problem if you distribute prebuilt binaries and you target all kinds of hardware. It is not that much of a problem if you...

OK, I will move to runtime compilation then (besides, I am planning changing the architecture so that GPU host code is organized as loadable plugins instead of being built in...

Yep, right now if you wish to distribute binaries, you have to own at least one AMD GPU and the newest possible Nvidia GPU and that sucks. This will change...