Hello O. Hartmann,
I didn't mean to be "rude" when closing that pocl issue report,
but there just seems to be no doubt that the problem is in the
LLVM-side and has wider impact than pocl or other OpenCL implementations.
Thus, the issue is better discussed in the LLVM bugzilla entries
instead of pocl's issue tracker / mailing list because other LLVM devs
are better be in the loop.
One easy "workaround fix" might be what I mentioned
in https://bugs.llvm.org/show_bug.cgi?id=30587:
"This error would probably just go away if the command line handler just
ignored multiple identical command line switch registrations silently."
Someone just needs to try something like that out and submit a patch to
LLVM. However, if the old dynlib linking doesn't work around it, there
might be a more serious / another issue now. And I'm not aware of
other client-side workarounds other than all clients dynamic linking
to the same libLLVM*.so, unfortunately.
BR,
Pekka
On 27.12.2017 15:19, O. Hartmann wrote:
Hello List.
Running pocl 0.14 and/or pocl-1.0 on FreeBSD CURRENT, using
CLANG/LLVM 4.0.1, code generated using pocl in combination with
ocl-icd 2.2.11 and intel-beignet and clover installed as additional
OpenCL ICDs, any code/binary using ocl-icd is bailing out when pocl
is installed dropping:
: CommandLine Error: Option 'enable-value-profiling' registered more
than once! LLVM ERROR: inconsistency in registered CommandLine
options
to the console.
Searching the net for some answers or bugfixes lead me to this bug
report:
https://github.com/pocl/pocl/issues/474
which has been closed (in a rude way for my taste).
There are reports similar to my experiences at the LLVM bug report
site:
Bug 30587 - Inconsistency in commandline options with multiple OpenCL
vendor libraries installed
https://bugs.llvm.org/show_bug.cgi?id=30587
with some comments from some fellows well known to this list and this
one:
Bug 22952 - cl::opt + LLVM_BUILD_LLVM_DYLIB is completely broken
https://bugs.llvm.org/show_bug.cgi?id=22952
I think I'm in the same boat now and want to ask if there is any
solution to this problem apart from staically linking llvm?
Kind regard,
Oh
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ pocl-devel mailing
list [email protected]
https://lists.sourceforge.net/lists/listinfo/pocl-devel
--
Pekka
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
pocl-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pocl-devel
