search for: libopencl

...x86_64from epel. >>> I tried to roll back to the previous version via yum history undo but >>> previous versions are no longer avaialble. >>> >> >> Do they have a hard coded Requires for the ocl-icd package or just an >> auto-generated Requires for the libOpenCL.so lib? >> >> If it's the former then the packages in epel need fixing. If it's the >> latter then the nvidia package will meet that requirement. You can >> either force uninstall ocl-icd, or uninstall ocl-icd and any >> dependencies, install/update the nvid...

...ibs because they need > ocl-icd-2.2.12-1.el7.x86_64from epel. > I tried to roll back to the previous version via yum history undo but > previous versions are no longer avaialble. > Do they have a hard coded Requires for the ocl-icd package or just an auto-generated Requires for the libOpenCL.so lib? If it's the former then the packages in epel need fixing. If it's the latter then the nvidia package will meet that requirement. You can either force uninstall ocl-icd, or uninstall ocl-icd and any dependencies, install/update the nvidia packages and then reinstall the package...

...b in llvm::Linker::LinkModules(llvm::Module*, llvm::Module*, std::function<void (llvm::DiagnosticInfo const&)>) () > from /opt/buildbot/lib/libLLVM-3.6svn.so > #16 0x00007ffff6c9d8cf in clang::BackendConsumer::HandleTranslationUnit(clang::ASTContext&) () from /opt/buildbot/lib/libOpenCL.so.1 > #17 0x00007ffff6e61f23 in clang::ParseAST(clang::Sema&, bool, bool) () from /opt/buildbot/lib/libOpenCL.so.1 > #18 0x00007ffff6c9e6bb in clang::CodeGenAction::ExecuteAction() () from /opt/buildbot/lib/libOpenCL.so.1 > #19 0x00007ffff6b7ead6 in clang::FrontendAction::Execute() ()...

The `Metadata`/`Value` split (PR21532) landed in r223802 -- at least, the C++ side of it. This was a rocky day, but I suppose that's what I get for failing to stage the change in smaller pieces. As of r223916 (lldb), I'm not aware of any remaining (in-tree) breakage, so if I've missed some problem in the sea of buildbot errors, please flag me down. I'll follow up soon with

...er::LinkModules(llvm::Module*, llvm::Module*, std::function<void (llvm::DiagnosticInfo const&)>) () >>> from /opt/buildbot/lib/libLLVM-3.6svn.so >>> #16 0x00007ffff6c9d8cf in clang::BackendConsumer::HandleTranslationUnit(clang::ASTContext&) () from /opt/buildbot/lib/libOpenCL.so.1 >>> #17 0x00007ffff6e61f23 in clang::ParseAST(clang::Sema&, bool, bool) () from /opt/buildbot/lib/libOpenCL.so.1 >>> #18 0x00007ffff6c9e6bb in clang::CodeGenAction::ExecuteAction() () from /opt/buildbot/lib/libOpenCL.so.1 >>> #19 0x00007ffff6b7ead6 in clang::Fron...

...lvm::Module*, llvm::Module*, std::function<void (llvm::DiagnosticInfo const&)>) () > >>>> from /opt/buildbot/lib/libLLVM-3.6svn.so > >>>> #16 0x00007ffff6c9d8cf in clang::BackendConsumer::HandleTranslationUnit(clang::ASTContext&) () from /opt/buildbot/lib/libOpenCL.so.1 > >>>> #17 0x00007ffff6e61f23 in clang::ParseAST(clang::Sema&, bool, bool) () from /opt/buildbot/lib/libOpenCL.so.1 > >>>> #18 0x00007ffff6c9e6bb in clang::CodeGenAction::ExecuteAction() () from /opt/buildbot/lib/libOpenCL.so.1 > >>>> #19 0x0000...

...llvm::Module*, std::function<void (llvm::DiagnosticInfo const&)>) () >>>>>>> from /opt/buildbot/lib/libLLVM-3.6svn.so >>>>>>> #16 0x00007ffff6c9d8cf in clang::BackendConsumer::HandleTranslationUnit(clang::ASTContext&) () from /opt/buildbot/lib/libOpenCL.so.1 >>>>>>> #17 0x00007ffff6e61f23 in clang::ParseAST(clang::Sema&, bool, bool) () from /opt/buildbot/lib/libOpenCL.so.1 >>>>>>> #18 0x00007ffff6c9e6bb in clang::CodeGenAction::ExecuteAction() () from /opt/buildbot/lib/libOpenCL.so.1 >>>>&g...

...t;> I tried to roll back to the previous version via yum history undo but > >>> previous versions are no longer avaialble. > >>> > >> > >> Do they have a hard coded Requires for the ocl-icd package or just an > >> auto-generated Requires for the libOpenCL.so lib? > >> > >> If it's the former then the packages in epel need fixing. If it's the > >> latter then the nvidia package will meet that requirement. You can > >> either force uninstall ocl-icd, or uninstall ocl-icd and any > >> dependencies, i...

...to roll back to the previous version via yum history undo but >>>>> previous versions are no longer avaialble. >>>>> >>>> >>>> Do they have a hard coded Requires for the ocl-icd package or just an >>>> auto-generated Requires for the libOpenCL.so lib? >>>> >>>> If it's the former then the packages in epel need fixing. If it's the >>>> latter then the nvidia package will meet that requirement. You can >>>> either force uninstall ocl-icd, or uninstall ocl-icd and any >>>>...

...t; ocl-icd-2.2.12-1.el7.x86_64from epel. >> I tried to roll back to the previous version via yum history undo but >> previous versions are no longer avaialble. >> > > Do they have a hard coded Requires for the ocl-icd package or just an > auto-generated Requires for the libOpenCL.so lib? > > If it's the former then the packages in epel need fixing. If it's the > latter then the nvidia package will meet that requirement. You can > either force uninstall ocl-icd, or uninstall ocl-icd and any > dependencies, install/update the nvidia packages and then...

On Wed, Mar 06, 2019 at 07:26:42AM -0500, Pete Geenhuizen wrote: > > On 03/02/2019 05:41 AM, Phil Perry wrote: > > > >Hi Gerry, > > > >I've updated the nvidia 340xx legacy package set for el7.6, and > >released the packages to the elrepo testing repository. > > > >Please could you test them and let me know if they work as > >expected. To

...ctly as it was on the screen > As John said, you are mistaken: $ rpm -qp --requires nvidia-x11-drv-304xx-304.135-1.el6.elrepo.x86_64.rpm /bin/sh /bin/sh /bin/sh /bin/sh /bin/sh /sbin/ldconfig /usr/bin/python config(nvidia-x11-drv-304xx) = 304.135-1.el6.elrepo grubby grubby libGL.so.1()(64bit) libOpenCL.so.1()(64bit) libX11.so.6()(64bit) libXext.so.6()(64bit) libXv.so.1()(64bit) libXvMC.so.1()(64bit) libXvMCNVIDIA_dynamic.so.1()(64bit) libatk-1.0.so.0()(64bit) libc.so.6()(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libcuda.so.1()(64bit) libdl.so.2()(64bit) libdl.so.2(GLIBC_2.2.5)(64bit) libgcc_s.so.1()(6...

Dear all, In the official document <https://llvm.org/docs/CompileCudaWithLLVM.html>, it is mentioned that CUDA compilation is supported on Windows as of 2017-01-05. I used msys2 to install clang 5.0.1. Then I installed cuda 8.0. However, I basically could not compile any code of cuda by the prescribed setting. I wounder if anyone can successfully compile cuda code by the clang on Windows.

Dear all, After a huge amount of time trying to install LLVM and Clang i could finally do it, so now im trying to use this tools for generating a bytecode, then apply it modular optimizations and then generate an executable to test the result. First, I only want to compile a project and execute it to see how it works, specifically this one:

...gt; > $ rpm -qp --requires nvidia-x11-drv-304xx-304.135-1.el6.elrepo.x86_64.rpm > /bin/sh > /bin/sh > /bin/sh > /bin/sh > /bin/sh > /sbin/ldconfig > /usr/bin/python > config(nvidia-x11-drv-304xx) = 304.135-1.el6.elrepo > grubby > grubby > libGL.so.1()(64bit) > libOpenCL.so.1()(64bit) > libX11.so.6()(64bit) > libXext.so.6()(64bit) > libXv.so.1()(64bit) > libXvMC.so.1()(64bit) > libXvMCNVIDIA_dynamic.so.1()(64bit) > libatk-1.0.so.0()(64bit) > libc.so.6()(64bit) > libc.so.6(GLIBC_2.2.5)(64bit) > libcuda.so.1()(64bit) > libdl.so.2()(64bit...

...17.3.6-1.fc27 @updates mesa-libEGL.x86_64 17.3.6-1.fc27 @updates mesa-libGL.x86_64 17.3.6-1.fc27 @updates mesa-libGLU.x86_64 9.0.0-13.fc27 @fedora mesa-libOpenCL.x86_64 17.3.6-1.fc27 @updates mesa-libgbm.x86_64 17.3.6-1.fc27 @updates mesa-libglapi.i686 17.3.6-1.fc27 @updates mesa-libglapi.x86_64 17.3.6-1.fc27 @update...

...e: > https://github.com/rsnemmen/OpenCL-examples/tree/master/add_numbers > > As I can see, it has a Makefile which you could use. Anyway, on Linux you > need to do something like: > > clang -std=c99 add_numbers.c -lOpenCL -I/path/to/folder/with/CL/cl.h > > > > Usually, libOpenCL.so and CL/cl.h are provided by OpenCL SDKs from HW/SW > vendor, for example: [1], [2], [3], [4] and others [5] > > But, you can also get them from KhronosGroup repos: OpenCL-ICD-Loader [6], > OpenCL-Headers [7] > > > > > I want to do that the .c file uses the .cl that i h...

On Thu, 8 Feb 2018, Felipe Westfields wrote: > I'm on a network that is disconnected from the internet; makes things kind > of awkward sometimes. We have some internal repositories that are supposed > to mirror centos, and EPEL - don't have one (that I'm aware of) that > mirrors elrepo. > But it looks like it's looking for just that one package; if that's all I

...jobs are submitted to CUPS directly instead of requiring the 'lpr' command-line tool. - There is support for managing multiple .NET runtime versions and their corresponding Mono versions. *** New external dependencies - The XInput 2 library is used for mouse control in games. - The libopencl library is used by the OpenCL wrapper dll. - The libgettextpo library is optionally used at build time to update po files from the rc sources. - The msgfmt tool (from the gettext library) is used at build time to compile po files. - The zlib library is used to implement cabinet file compress...

Hi Tobias, I didn't really get it. Is the idea that the same bitcode is going to be codegen'd for different architectures, or is each sub-module going to contain different bitcode? In the later case you may as well just use multiple modules, perhaps in conjunction with a scheme to store more than one module in the same file on disk as a convenience. Ciao, Duncan. > a couple of weeks