Den Wed, 16 Oct 2013 07:38:18 -0700 skrev Re: [pocl] Raspberry pi (#12): > Yeah, and AFAIK the ARM situation with the calling conventions / ABI > is even more hairy than with x86_64. @kraiskil might confirm that.
Yes, but only as long as we don't use SPIR. >From the SPIR docs: "SPIR kernels should use "spirkrnl" calling convention. Non-kernel functions use "spirfnc" calling convention. All other calling conventions are disallowed." So, going into the kernel, we should not have any ABI issues (except how we call a spirkrnl-style function in the first place, but that needs to be solved anyways). We might have problems if/when we make system calls *from* the kernel, (e.g. printf), which do use platform-specific ABIs. But I think printf is the only one (apart from a clEnqueueNativeKernel-kernel) where this pops up (??), and the pre-built kernels functions do not call either of these non-SPIR-ABI functions, so from this part the kernels library can be made portable. And if the builtins can be restricted to processor-independent ones without losing performance, we should be all set. kalle p.s. adding the mailinglist to the CC :) ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk _______________________________________________ pocl-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pocl-devel
