Beatriz Navidad Vilches

Rules for functions go from F.21 to F.60 and then go back to F.22:  Is this intentional or is it a bug?

Adds a CMake module with the packaging configuration and "Package" and "Consume" steps to GitHub actions to check that it works as it should.

In some samples, namely `binaries`, `blur`, `reduce`, `multi-device` and `saxpy` from `samples/core`, compile-time checks like the following ``` #if CL_HPP_TARGET_OPENCL_VERSION >= 200 cl_command_queue_properties props[] = { CL_QUEUE_PROPERTIES, CL_QUEUE_PROFILING_ENABLE, 0 };...

[Issue]: Scan test failure in rocThrust caused by changes in LLVM for the ROCm 6.2.1 release

2

### Problem Description [One of rocThrust's tests](https://github.com/ROCm/rocThrust/blob/develop/testing/scan.cu#L531) for the scan algorithm is failing right after the ROCm 6.2.1 release. During debugging, it was noticed that modifying the [addition operator of...

MIOpen error tolerance

6

## Scope While testing the variant 0 for bnorm backward spatial single, we observed that the error tolerance in MIOpenDriver is sub-optimal. For instance, the following results were observed ```shell...