Intel® Integrated Performance Primitives
Deliberate problems developing high-performance vision, signal, security, and storage applications.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.

creating 64bit custom dll

bendeguy
Beginner
809 Views

Hi!

I've succesfully made 32bit custom dlls from some IPP function(using the Intel IPP features linkage usage models for Custom DLLs and Merged Static Libraries sample) for any 32 bit architecture. My problem is with 64 bit architecture. I changed everything(in the sample)according to the 64bit M7 architecture, but when Icompiledthe dll, I got the following errors:

d:mpeg-4vc++audiovideoippcorelibrary64srcfunclist.h(9) : error C2485: 'naked' : unrecognized extended attribute
d:mpeg-4vc++audiovideoippcorelibrary64srcfunclist.h(9) : error C4235: nonstandard extension used : '__asm' keyword not supported on this architecture
d:mpeg-4vc++audiovideoippcorelibrary64srcfunclist.h(9) : error C2065: 'jmp' : undeclared identifier
d:mpeg-4vc++audiovideoippcorelibrary64srcfunclist.h(9) : error C2146: syntax error : missing ';' before identifier 'dippiDeinterlaceFilterTriangle_8u_C1R'

and so on. It looks like __asm and naked not supported on 64 machines. Can anyone help me how to build my dll?

Thanks in advance,

Bendeguy

0 Kudos
1 Reply
Vladimir_Dudnik
Employee
809 Views

Hi Bendeguy,

first of all, you can submit your request for sample custom DLL for x64 systems through Intel Premier Support

Actually, we are working on such sample. On x64 systems you need to build custom DLL in a bit different way, not as it was in 32-bit sample.

You can create simple DLL project with DllMain function, and call ippStaticInit() at DLL initialization time. You need to link this project with IPP merged and emerged libraries and you need to add export.def file to this project. In this export.def file you only list functions you are interested in, and so only those functions will be included into DLL binary at link stage.

Regards,
Vladimir

0 Kudos
Reply