https://bugs.llvm.org/show_bug.cgi?id=45401

            Bug ID: 45401
           Summary: Target CUDA RTL --> CUDA error is: named symbol not
                    found
           Product: OpenMP
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: Runtime Library
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]

I got from LIBOMPTARGET_DEBUG=1 output

Target CUDA RTL --> Load data from image 0x000000000096ab50
Target CUDA RTL --> CUDA module successfully loaded!
Target CUDA RTL --> Loading
'__omp_offloading_29_37ac7ea__ZN11qmcplusplus12SplineC2ROMPIfE19evaluateVGLMultiPosERKNS_6VectorIfNS_12OMPallocatorIfNS_23CUDALockedPageAllocatorIfNS_10MallocatorIfLm64EEEEEEEEERKSt6vectorISt17reference_wrapperINS2_IfSaIfEEEESaISG_EERKSC_ISD_INS2_INS_10TinyVectorIfLj3EEESaISM_EEEESaISP_EESK__l103'
(Failed)
Target CUDA RTL --> CUDA error is: named symbol not found
Libomptarget --> Unable to generate entries table for device id 0.

caused by the following function in a class.
  void evaluateVGLMultiPos(const Vector<ST, OffloadPinnedAllocator<ST>>&
multi_pos_copy,
                           const RefVector<ValueVector_t>& psi_v_list,
                           const RefVector<GradVector_t>& dpsi_v_list,
                           const RefVector<ValueVector_t>& d2psi_v_list)
  {
    #pragma omp target
    {    }
  }

The same class do have another target region which works fine if I comment out
the above target region.
  void finalizeConstruction() override
  {
    #pragma omp target
    {     }
  }

Here I was not using static linking but directly linking the object file into
the final executable.

I also wondered if the long mangled name was the issue. But adding many
characters to finalizeConstruction didn't seem to cause any issue when I tried.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

Reply via email to