|
| From: | Cuvelier Francois |
| Subject: | Re: Octave and GPU |
| Date: | Mon, 21 Nov 2016 06:16:12 +0100 |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 |
|
Le 21/11/2016 à 04:20, Mike Miller a
écrit :
On Sat, Nov 19, 2016 at 09:13:36 +0100, Cuvelier Francois wrote: […]The delete function is not call when using clear command Do you plan to write the missing code in the function handle_delete in file libinterp/octave-value/ov-classdef.cc ?Yes, this is tracked by an open bug report: https://savannah.gnu.org/bugs/?46497 Feel free to subscribe to that bug tracker, or submit a patch to provide the missing functionality. In the meantime, calling `delete(obj)` before clearing the object should give the desired results. It is not a satisfactory solution. For example,
if X is a mThrust object (contains a pointer to an array on
GPU memory) the operation in Octave: Y=(X+1)+2 Create a new mThrust object Y (OK) but when evaluating right operand (X+1) create a temporary mThrust object with allocation on GPU. Without the bug corrected the temporary mThrust object is "deleted" without desallocation on GPU!
|
| [Prev in Thread] | Current Thread | [Next in Thread] |