I'll let this to later, as we will need to check all the code anyway if we
do something like that. And in all case, if you play with the internal that
is hidden, people won't be surprised too much if they start to have
problems.


On Thu, Apr 17, 2014 at 2:07 PM, abergeron <notifications@github.com> wrote:

> In theano/sandbox/cuda/cuda_ndarray.cu:
>
> >                      contiguous_self->devdata, 1,
> > -                    PyArray_DATA(rval), 1);
> > -    CNDA_THREAD_SYNC;
> > +                    rval_data, 1);
>
> I don't necesserly mean other threads executing the same function. Other
> threads can reach inside the theano function object and play with the
> output_storage values.
>
> But we could always just leave it at "don't do that or you might get
> crashes". Also, the way I see it we don't know exactly how the code will
> evolve in the future so it is a kind of future-proofing. If you prefer that
> we do this later if we ever need it, then ok.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/Theano/Theano/pull/1809/files#r11745261>
> .
>