Hi Dmitry, Thanks for the response. My experience matches your description.
Just for background, In terms of generic targets, the only one I'm currently very interested in is the single-lane target. I have an application that has both single-lane and multi-lane code paths. I pretty easily workaround the lack of a working single lane target just by making all uniform versions of my functions. This usually requires me to make use of #define macros when writing functions (to appropriately substitute uniform and varying) - which is a bit ugly - and this is what I was trying to find an alternative for. I was experimenting with using the generic-x1 target to compile what is essentially an all uniform verison of my functions. The generic-x1 path from .ispc -> .bc -> .o worked pretty well (some internal __vselect functions were improperly given global scope). But a non-functioning -O0 option makes symbolic debugging pretty awful with this approach. Now if we had template functions...... ;-> -Brian On Sunday, November 5, 2017 at 12:01:00 AM UTC-7, Dmitry Babokin wrote: > > Generic targets are not well maintained and there are multiple known > failures. And I don't think that's going to change. > > On Thu, Nov 2, 2017 at 5:12 PM, Brian Green <[email protected] > <javascript:>> wrote: > >> I am encountering a crash when combining the generic-x1 target at the -O0 >> flag. For example: >> >> foo.ispc: >> >> void foo() >> { >> } >> >> ispc foo.ispc --target=generic-x1 --emit-c++ -o foo.cc >> >> works fine. But... >> >> ispc foo.ispc --target=generic-x1 --emit-c++ -o foo.cc -O0 >> >> gives: >> >> llvmutil.cpp:1560: Assertion failed: "llvm::isa<llvm::Instruction>(v) == >> true". >> *** >> *** Please file a bug report at https://github.com/ispc/ispc/issues >> *** (Including as much information as you can about how to reproduce this >> error). >> *** You have apparently encountered a bug in the compiler that we'd like >> to fix! >> *** >> main.cpp(235): FATAL ERROR: Unhandled signal sent to process; terminating. >> Abort (core dumped) >> >> Any ideas? >> >> -Brian >> >> -- >> 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] <javascript:>. >> 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.
