Torsten Keßler

Hey Ron, thank you very much for your quick reply. Applying your changes I get a segmentation fault because `printf()` tries to access memory on allocated the device. The code...

Update: With the new 11.8-0 release I get the following error ```bash x[9] = 9 [/build/aomp-amdgpu/src/amd-llvm-project/openmp/libomptarget/plugins/hsa/impl/data.cpp:99] atmi_malloc failed: HSA_STATUS_ERROR_INVALID_ARGUMENT ```

Update for 11.9-0: ``` x[9] = 9 [/build/aomp-amdgpu/src/amd-llvm-project/openmp/libomptarget/plugins/hsa/impl/data.cpp:100] atmi_malloc failed: HSA_STATUS_ERROR_INVALID_ARGUMENT ```

Update for 11.11-0: ```bash x[9] = 9 [/build/aomp-amdgpu/src/amd-llvm-project/openmp/libomptarget/plugins/amdgpu/impl/data.cpp:61] atmi_malloc failed: HSA_STATUS_ERROR_INVALID_ARGUMENT ```

@gregrodgers: I've tested the following examples with `clang`from the latest ROCm docker image and with aomp-13.0-2 compiled from source with kernel 5.12.5 (Arch Linux) on a Vega 56. @ronlieb :...

Yes @carlobertolli, my sample programs work with the latest release. Thank you!

Hi! I'm packaging ROCm for Arch Linux and I'm running in the same issue with doxygen 1.9.6 and TeX live 2022.

Hi! I'm packaging ROCm for Arch Linux and we hit the same problem. The Debian folks also discuss this on their [mailing list](https://lists.debian.org/debian-ai/2022/05/msg00026.html). @cgmb @Maxzor

@nlohmann Do you have an update for us on this issue? As @dvzrv said, we'd like to avoid using unsigned tar archives. With git, you can use David's suggestion: >...

Friendly ping @nlohmann :) As discussed above, you'd do us and the Arch community a great favor if you'd properly sign your releases.