> On Dec 3, 2018, at 8:39 PM, Vasco Alexandre da Silva Costa > <vasco.co...@gmail.com> wrote: > > Hey, > Did anyone check to see if the OpenCL librt backend works after the > threads changes? Last I tried to, like last GSoC, it was broken. Any > OpenCL library calls need to be made in thread 0 in an MT environment. > Which was likely not the case.
What threading changes? I’ve not tested the OpenCL backend MT, but there haven’t been any significant threading changes in LIBBU. > Anyway, since AFAIK this is not considered to be a critical issue ATM, > if it is not fixed yet we can work in it for the next release and > meanwhile continue on the branch. Not critical only because it’s all still sitting disabled in a separate mode of compilation and on a branch, not in user hands. It’d be really great to get those speed gains going for everyone. I’m really curious how well it would work with the real-time ray tracing demo interface I have working via ospray. On a related note, I’d like to get us back on track releasing more frequently, even if new features are incomplete. The past couple years we got off track as priorities shifted around with some customers and that hurt development. The longer we went without releasing, the harder, more expensive, and burdensome release became. Nothing unobvious or surprising. I’d like to see us back to releasing monthly, which is going to require some conscious community effort. Early this new year we’ll likely see migration to git, new gui work started, continuous integration setup, and a contest. Cheers! Sean _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
