Jacob Lambert

@pfultz2 closing this pull request for now. If you think this change is still desirable we can reopen and investigate. Thanks!

This should be fixed in recent releases. If anyone is still hitting an issue with this please comment and I can reopen!

It could be nice to have two different error enums for invalid action and invalid action argument, but at this point the disruption it would cause may not be worth...

https://github.com/RadeonOpenCompute/ROCm-CompilerSupport/commit/5b684e557c67ef1a8482117c462ed25ac4a805d6

I'm guessing this is no longer an issue. I haven't seen or heard of this error recently. Follow up if you're still able to recreate it though!

Hi, thanks for looking into this! It looks like you're using the following: AMD Radeon RX 6950 XT Arch Linux rocm 5.2.0 installed via arch linux packages (paru?) I'll see...

The log should write to the file path assigned to AMD_COMGR_REDIRECT_LOGS (I usually use AMD_COMGR_REDIRECT_LOGS=stdout, but you can pick any file). Another thing you can try that would be helpful...

Looking into this now! In your log file it looks like the input file name is cut off right at the end. Is this just an artifact of the application...

I believe I've been able to recreate this issue locally now. A minimal reproducer based on your temporary files: ``` clang "-cc1" \ "-include-pch" "./comgr-ee6420/include/hip.pch" "-fno-validate-pch" \ "-I" "./comgr-ee6420/include" \...

Is this still an issue with recent versions of ROCm? If so can you reopen here and I'll take another look? [https://github.com/ROCm/llvm-project/tree/amd-staging/amd/comgr](https://github.com/ROCm/llvm-project/tree/amd-staging/amd/comgr) Quickly testing the following doesn't give me any...