-
-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[arch] [beignet] CommandLine Error: Option 'help-list' registered more than once! #55
Comments
Its an llvm version mismatch between multiple modules that both link to LLVM, just not, the same LLVM. I never found a good solution to this yet, but I found a possible solution or two (that I havent tried), which is described at #29 (comment) . Related/similar/same issue: jrprice/Oclgrind#137 |
Hmm, the fix you proposed seems fairly complex. If the issue is that coriander doesn't use the same version of llvm as the driver/other(?), why don't we allow for coriander to be compiled using any (relevant) llvm version? Renaming the symbols sounds like it will bring more issues than it will solve. |
Its a single
because each version has a different API. Not incredibly different, but incompatibly different. |
see this comment: #29 (comment) and the following one: "By the way, you might be able to simply add, in the CMakeLists.txt:
" |
Similar bugs seen elsewhere were the opposite: two parts of an application loading the same LLVM version, which causes them to share global LLVM state that isn't intended to be shared. This is really an LLVM bug, but fixing it there appears to be difficult. It is not specific to coriander: if multiple OpenCL ICDs are installed, it affects even simple OpenCL applications. Debian beignet avoids this problem (since Debian 9/Ubuntu 17.04) by statically linking to LLVM; you may want to suggest that Arch beignet do the same. |
With "add_definitions(-Dllvm=llvm40)" |
The following error comes up when running
make run-tests
I've not tested this on ubuntu and my rx 470 doesn't show this issue.
The text was updated successfully, but these errors were encountered: