Bug 241482 - lang/pocl: failed with 'Undefined symbol "clGetPlatformInfo"'
Summary: lang/pocl: failed with 'Undefined symbol "clGetPlatformInfo"'
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs mailing list
URL:
Keywords: needs-qa, regression
Depends on:
Blocks: 241243
  Show dependency treegraph
 
Reported: 2019-10-25 02:42 UTC by Jan Beich
Modified: 2019-10-26 10:10 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (ohartmann)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Beich freebsd_committer 2019-10-25 02:42:17 UTC
$ pkg install pocl clpeak
$ clpeak

Platform: Portable Computing Language
  Device: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
    Driver version  : 1.4 (FreeBSD)
    Compute units   : 8
    Clock frequency : 4601 MHz

    Global memory bandwidth (GBPS)
      float   : clEnqueueNDRangeKernel (-63)
      Tests skipped

    Single-precision compute (GFLOPS)
clCreateBuffer (-61)
      Tests skipped

    No half precision support! Skipped

    Double-precision compute (GFLOPS)
clCreateBuffer (-61)
      Tests skipped

    Integer compute (GIOPS)
clCreateBuffer (-61)
      Tests skipped

    Transfer bandwidth (GBPS)
      enqueueWriteBuffer         : 0.00
      enqueueReadBuffer          : 0.00
      enqueueMapBuffer(for read) : 0.00
        memcpy from mapped ptr   : inf
      enqueueUnmap(after write)  : 0.00
        memcpy to mapped ptr     : inf

    Kernel launch latency : dlopen("/home/foo/.cache/pocl/kcache/JH/IDMFGLODMLKNOOOIDKINDHECPPKMGBKLEIOBN/global_bandwidth_v1_local_offset/256-1-1-goffs0-smallgrid/global_bandwidth_v1_local_offset.so") failed with 'Undefined symbol "clGetPlatformInfo"'.
note: missing symbols in the kernel binary might be reported as 'file not found' errors.
Abort trap
Comment 1 Jan Beich freebsd_committer 2019-10-25 02:50:45 UTC
Not reproducible with 1.3 (previous version).
Comment 2 O. Hartmann 2019-10-26 10:10:59 UTC
It affects me, too. Think this is a bug affecting many people.