Hi Dmitry, Thanks for this. I've taken a look at your branch and I don't believe that most of the changes would be needed in my case, since I'm only changing the object file format, not defining a new CPU type. I am currently thinking of adding a command-line option to specify the default target triple to use (dropping back to llvm::sys::getDefaultTargetTriple() if not specified). The only thing that I'm not clear on is the compilation of builtins.c and gen-stdlib-mask*.cpp. I see that these are built in ispc.vcxproj and the target triple is provided to the command. I'm not sure quite what these are and whether it is possible to achieve what I am attempting (that is, a single ispc.exe capable to generating both MSVC and GCC object files depending on the invocation).
If you could provide any more help and thoughts, I would be very grateful. Cheers, Steve. On Saturday, 12 May 2018 09:52:31 UTC+1, Dmitry Babokin wrote: > > Hi, > > You've got it pretty much right, you need to define target triple to the > target platform that you need and you are almost done. But there are other > minor issues. We are building PS4 target, which is Windows cross compiler > targeting FreeBSD. You can have a look at this branch > https://github.com/dbabokin/ispc/tree/jaguar_v192 for more details. > > Looks like it's the time add a How To page about building cross compilers. > > Dmitry. > > -- 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 ispc-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
