I'm not sure what this example is, I assume it's from embree. You need to supply these functions to make it work. ISPC philosophy is not to invent the wheel when it comes to task parallelism, but to work with any existing task parallelism system that user would like to use. And these 3 functions is ISPC interface to user-provided task parallelism runtime. And typically you can just pick one from examples/tasksys.cpp. So they have to be provided in one or other way. Though embree may have it's own implementation for it, but I'm not sure about that.
On Tue, May 22, 2018 at 12:34 AM, Bruno Martins <[email protected]> wrote: > I am following triangle_geometry_device tutorial that uses the same > functions and remember to use them without cpp implemention. Am i missing > something? > > Best Regards > Bruno > > On 21 May 2018 at 23:22, Dmitry Babokin <[email protected]> wrote: > >> You are using task parallelism. To make it work, you need to provide >> implementation of ISPCAlloc/ISPCLaunch/ISPCSync. There's reference >> implementation with different underlying runtime libraries in >> examples/tasksys.cpp >> >> More info here: >> http://ispc.github.io/ispc.html#task-parallelism-runtime-requirements >> >> On Mon, May 21, 2018 at 7:57 AM, Bruno Martins <[email protected]> >> wrote: >> >>> Hello, >>> >>> Another question: >>> >>> when i am trying to link the program that i wrote with ispc against my >>> VS project this errors appear: >>> >>> 1>program.obj : error LNK2019: unresolved external symbol ISPCAlloc >>> referenced in function render___un_3C_unf_3E_uniun_3C >>> _unf_3E_uniun_3C_uni_3E_un_3C_uni_3E_ >>> 1>program.obj : error LNK2019: unresolved external symbol ISPCLaunch >>> referenced in function render___un_3C_unf_3E_uniun_3C >>> _unf_3E_uniun_3C_uni_3E_un_3C_uni_3E_ >>> 1>program.obj : error LNK2019: unresolved external symbol ISPCSync >>> referenced in function render___un_3C_unf_3E_uniun_3C >>> _unf_3E_uniun_3C_uni_3E_un_3C_uni_3E_ >>> >>> Am I missing something when i am using ispc compiler? >>> >>> Best, >>> Bruno >>> >>> >>> On 18 May 2018 at 08:21, Bruno Martins <[email protected]> wrote: >>> >>>> hello, >>>> >>>> The issue is fixed. >>>> Thank you for your support. >>>> >>>> Best, >>>> Bruno >>>> >>>> On 18 May 2018 at 08:07, Steve Hill <[email protected]> wrote: >>>> >>>>> I've managed to successfully link an object produced with ispc v1.9.2 >>>>> using MSVS2017. Possibly silly question but you are trying to link into a >>>>> 64-bit project, not 32-bit; correct? >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Intel SPMD Program Compiler Users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Intel SPMD Program Compiler Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Intel SPMD Program Compiler Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Intel SPMD Program Compiler Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Intel SPMD Program Compiler Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
