Now is 0.15.

AMD released new AOCC compiler, with support to the latest cpus.

For Ralph and Rosetta, CPU optimizations look more worthwhile. For many other BOINC projects, trying GPU versions looks worthwhile.

What's new with 0.09 version??

<message>
app_version download error: couldn't get input files:
<file_xfer_error>
<file_name>boinc_app_v3</file_name>
<error_code>-120 (RSA key check failed for file)</error_code>
<error_message>signature verification failed</error_message>
</file_xfer_error>
</message>

<message>
upload failure: <file_xfer_error>
<file_name>dt_RAH_test_0_1674_1_1_r1545932415_0</file_name>
<error_code>-240 (stat() failed)</error_code>
</file_xfer_error>
<file_xfer_error>
<file_name>dt_RAH_test_0_1674_1_1_r1545932415_1</file_name>
<error_code>-240 (stat() failed)</error_code>
</file_xfer_error>
<file_xfer_error>
<file_name>dt_RAH_test_0_1674_1_1_r1545932415_2</file_name>
<error_code>-240 (stat() failed)</error_code>
</file_xfer_error>
<file_xfer_error>
<file_name>dt_RAH_test_0_1674_1_1_r1545932415_3</file_name>
<error_code>-240 (stat() failed)</error_code>
</file_xfer_error>
</message>

I've also read that the Rosetta developers do not want to deal with interpreting dumps from more versions of their applications, so I'd expect them not to want to do this.

Years ago, a major section was added to BOINC to allow running CUDA applications. Another major section was then added to allow running OpenCL applications. I'd expect this to be required for adding capability to run applications using any other GPU computer language, although it is possible that other GPU computer compilers could translate their requirements into using either the CUDA section or the OpenCL section instead, or have a library that can do these translations.
Some of the things that must be handled :

1. Which GPU to use, if the computer has more than one.
2. Any pauses or slowdowns needed to allow the user to do something else on the computer before the application finishes,
3. A way to abort the application if the current task appears to be trying to run forever.
4. Reporting the application's progress to BOINC.
.......
Since the clocks for GPUs on graphics boards are typically about a quarter of the speeds of CPU clocks, the GPU version could be as slow as a quarter of the speed of the CPU version if it had no two operations that could run simultaneously. But in that case, no BOINC project would be likely to offer that GPU version.
However if the maximum possible number of operations that could run simultaneously on that graphics board were compatible with the program, the GPU version could run as fast as a fourth of the CPU application multiplied by the number of GPU cores in the GPU. For some of the latest graphics boards, that could be a thousand times as fast as the CPU version.

Ten times as fast as the CPU version is more typical for GPU versions released by BOINC projects, though.

I've read that the Ralph@Home and Rosetta@Home applications have large collections of different software paths, many of which are not used in most tasks.
However, it should be possible to identify paths that are used the most and have the most possible speedup, and produce a forked version that uses only those paths, with GPU use where it is reasonable.
I've also read that the Rosetta developers do not want to deal with interpreting dumps from more versions of their applications, so I'd expect them not to want to do this.

Also, this would require the developers to produce a way to sort all of the tasks into those that can run on the GPU version and those that cannot.

Most of the alternate software packages mentioned here for GPU use under BOINC look usable if you want BOINC to start a task, and then have no control of that task until it finishes. But how many BOINC users want to allow that?

I've looked into getting the source code for the Ralph@Home and Rosetta@Home applications. It is allowed, but only for those who pay a fairly high price for it (several thousand dollars).

Do you feel it is reasonable to pay that much money to produce GPU versions that, so far, seem likely to run at roughly the same speed as the CPU versions?

HipSycl 0.9.0 has a lot of new features.
And HipSycl 0.9.1 will have more!

hipSYCL can compile to a single binary that runs on CPUs/AMD/NVIDIA/Intel GPUs!!

Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Out Of Memory (C++ Exception) (0xe06d7363) at address 0x00007FFAA177D759

Engaging BOINC Windows Runtime Debugger...

failed to download

<message>
WU download error: couldn't get input files:
<file_xfer_error>
<file_name>dummy.txt</file_name>
<error_code>-200 (wrong size)</error_code>
</file_xfer_error>
</message>

More details will be welcome