search for: setarg

...be called. For what it's worth, this issue manifests itself in an unsolved pocl bug: https://bugs.launchpad.net/pocl/+bug/987905 It would be simpler to implement a portable implementation for calling the kernel from the host if we could assume the kernel calling convention mapped each OpenCL setArg arg to a single kernel function arg (and preferably all arg data in memory). For the non-kernel functions it should not matter and could be target-specific. -- Pekka

...s worth, this issue manifests itself in an unsolved pocl > bug: https://bugs.launchpad.net/pocl/+bug/987905 > > It would be simpler to implement a portable implementation for calling the > kernel from the host if we could assume the kernel calling convention > mapped > each OpenCL setArg arg to a single kernel function arg (and preferably all > arg data in memory). For the non-kernel functions it should not matter and > could be target-specific. > -- Pekka

...t; >> bug: https://bugs.launchpad.net/pocl/+bug/987905 > >> > >> It would be simpler to implement a portable implementation for calling > the > >> kernel from the host if we could assume the kernel calling convention > >> mapped > >> each OpenCL setArg arg to a single kernel function arg (and preferably > all > >> arg data in memory). For the non-kernel functions it should not matter > and > >> could be target-specific. > >> > > > > > > -- > > Pekka > -------------- next part -----------...

...fests itself in an unsolved pocl >> bug: https://bugs.launchpad.net/pocl/+bug/987905 >> >> It would be simpler to implement a portable implementation for calling the >> kernel from the host if we could assume the kernel calling convention >> mapped >> each OpenCL setArg arg to a single kernel function arg (and preferably all >> arg data in memory). For the non-kernel functions it should not matter and >> could be target-specific. >> > > > -- > Pekka -------------- next part -------------- An HTML attachment was scrubbed... URL: <ht...

...t;>>> >>>> It would be simpler to implement a portable implementation for >>>> >>> calling the >> >>> kernel from the host if we could assume the kernel calling >>>> >>> convention >> >>> mapped each OpenCL setArg arg to a single kernel function arg (and >>>> >>> preferably all >> >>> arg data in memory). For the non-kernel functions it should not >>>> >>> matter and >> >>> could be target-specific. >>>> >>>> >...

...solved pocl >>> bug: https://bugs.launchpad.net/pocl/+bug/987905 >>> >>> It would be simpler to implement a portable implementation for > calling the >>> kernel from the host if we could assume the kernel calling > convention >>> mapped each OpenCL setArg arg to a single kernel function arg (and > preferably all >>> arg data in memory). For the non-kernel functions it should not > matter and >>> could be target-specific. >>> >> >> >> -- Pekka > > -- Pekka

...It would be simpler to implement a portable implementation for >>>>> >>>> calling the >>> >>>> kernel from the host if we could assume the kernel calling >>>>> >>>> convention >>> >>>> mapped each OpenCL setArg arg to a single kernel function arg (and >>>>> >>>> preferably all >>> >>>> arg data in memory). For the non-kernel functions it should not >>>>> >>>> matter and >>> >>>> could be target-specific. >&g...

...inen wrote: For what it's worth, this issue manifests itself in an unsolved pocl bug: https://bugs.launchpad.net/pocl/+bug/987905 It would be simpler to implement a portable implementation for calling the kernel from the host if we could assume the kernel calling convention mapped each OpenCL setArg arg to a single kernel function arg (and preferably all arg data in memory). For the non-kernel functions it should not matter and could be target-specific. -- Pekka -- Pekka -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/l...

> -----Original Message----- > From: mankeyrabbit at gmail.com [mailto:mankeyrabbit at gmail.com] On Behalf > Of James Molloy > Sent: Wednesday, September 12, 2012 12:18 PM > To: Ouriel, Boaz > Cc: cfe-dev at cs.uiuc.edu; llvmdev at cs.uiuc.edu; Villmow, Micah > Subject: Re: [cfe-dev] [LLVMdev] SPIR provisional specification is now > available in the Khronos website >

Hi, I'm trying to compile asterisk-oh323-0.7.1 in FreeBSD 5.3. I tried to use gmake but it exits with too many errors. Did somebody compile before oh323 in FreeBSD? How should I compile it under FreeBSD? thanks, Ganbold

...r/home/tsgan/pwlib/include/ptlib/args.h:215: error: expected `,' or `...' before '&' token /usr/home/tsgan/pwlib/include/ptlib/args.h:216: error: ISO C++ forbids declaration of `PStringArray' with no type /usr/home/tsgan/pwlib/include/ptlib/args.h:216: error: `void PArgList::SetArgs(int)' and `void PArgList::SetArgs(int)' cannot be overloaded /usr/home/tsgan/pwlib/include/ptlib/args.h:249: error: expected `,' or `...' before '&' token /usr/home/tsgan/pwlib/include/ptlib/args.h:254: error: ISO C++ forbids declaration of `PString' with no type /u...