On 01/11/2013 03:36 PM, Erik Schnetter wrote: > It may be that an object has a refcount of 2, and is then released > twice. The current code may then destroy the object twice, because both > threads see that the refcount is now 0. The user code is legal, this is > an error in pocl.
You are right, I didn't realize it reads the refcount *again* after the locked region to decide whether to free or not. I added a bug report: https://bugs.launchpad.net/pocl/+bug/1098575 -- Pekka ------------------------------------------------------------------------------ Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 _______________________________________________ pocl-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pocl-devel
