On 03/20/2013 10:03 PM, Erik Schnetter wrote: > I just realized that running pocl from its build directory is not independent > of > a previous install -- pocl will look into its install directory first, > potentially using outdated libraries.
That should not happen. I use this setup all the time during development. But I use Linux and ICD, I have not tested non-icd builds recently. > There are no calls to memcpy left in parallel.bc. Some functions are not > inlined, but this seems to be a reasonable decision by the compiler, since the > respective functions are not trivial. Everything should be inlined in parallel.bc except, e.g., printf for which we do not have an implementation in the kernel lib. Flatten.cc takes care of that. Seems to be the case here (when using the pocl's round). > Can you send me your "parallel.s" file (should live next to the parallel.bc) > for > me to look at? Send it in private, the file is large. OK. -- --Pekka ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ pocl-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pocl-devel
