• State Accepted Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 25 subscribers
  • Views 3927 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Arm Performance Libraries compatibility with MSVC

CristianPanaite

Hello!

I was trying to build PyTorch with APL using MSVC on a Windows machine and I encountered this error: 

error LNK2001: unresolved external symbol __divdc3

It seems like __divdc3 is a symbol specific to LLVM and it doesn't exist on MSCV.

Can you tell me if there is a way to make APL compatible with MSVC?

Parents
  • 0 in reply to adamsmithad

    I can't tell about performance on Windows but compatibility is tricky. I need a Fortran compiler. I build Classic Flang - its runtime files depend on MSVC's libomp140.aarch64.dll while the Flang OpenMP library is called libomp.dll. ArmPL's OpenMP library is called omp.dll. Which one to use? :)

    I guess I can recompile Flang a seconds time with itself to get rid of the libomp140.aarch64.dll dependency and then use ArmPL's libomp.dll which has the same name as Flang's. I haven't tested it yet. For me the problem is to get Flang working on Windows as it does on Linux. When I link a large number of Fortran object files, I get a lot of missing symbols. But this is a different discussion.

Reply
  • 0 in reply to adamsmithad

    I can't tell about performance on Windows but compatibility is tricky. I need a Fortran compiler. I build Classic Flang - its runtime files depend on MSVC's libomp140.aarch64.dll while the Flang OpenMP library is called libomp.dll. ArmPL's OpenMP library is called omp.dll. Which one to use? :)

    I guess I can recompile Flang a seconds time with itself to get rid of the libomp140.aarch64.dll dependency and then use ArmPL's libomp.dll which has the same name as Flang's. I haven't tested it yet. For me the problem is to get Flang working on Windows as it does on Linux. When I link a large number of Fortran object files, I get a lot of missing symbols. But this is a different discussion.

Children
No data