Michal Babej

> I'm not sure whether this is a bug in LLVM, POCL or both. Message is from LLVM, and it says certain debug information is missing in the bitcode. >...

AFAICT it should be OK to drop all LLVMs up to at least 11 (Ubuntu 20.04 LTS has LLVM 12 in repository).

> Is this only related to the PTX version supported by LLVM (version 11) I think that is correct. > Is upgrading LLVM to the latest version likely to address...

The first thing to try is to remove pocl's cache. Can you try ``rm -rf $HOME/.cache/pocl`` and see if it helps ?

Hello, I'm entirely unfamiliar with ParrotOS, and also what that patch does. I'm wildly assuming `noexec ${HOME}` somehow restricts executable files in the user's home directory ? That may interfere...

@PalinuroSec yes `/tmp` should work, i use it all the time. You'll likely want something per-user, like `/tmp/pocl-`, or perhaps `/run/user//pocl`. But any directory where you can write an executable...

Tested with release 1.8 branch, LLVM 13, cannot reproduce. Can you retest ?

> it looks like that this can work on 2nd way. Is that right what I understand? Yes, that is correct. PoCL doesn't support running on "bare metal" (without Linux...

There is a "-target" vs "--target" option detection in the CMakeLists somewhere, but either way, nobody tried to compile pocl (with LLVM) on Windows for years. So it *might* require...

@new2f7 some time ago, we added the "standard" (-O3) optimization passes early into the kernel pases, and they are now run before implicit-loop-barriers pass, which seems to interact with POCL_FORCE_PARALLEL_OUTER_LOOP....