[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #50105] __ilu__ and __ichol__ should use liboc
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #50105] __ilu__ and __ichol__ should use liboctave functions instead of feval |
Date: |
Wed, 9 Jan 2019 17:57:11 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko |
Follow-up Comment #6, bug #50105 (project octave):
Maybe this is too deep questions of the compiler, but isn't the pointer in the
original code valid throughout the parsing of the function call to ichol_t?
In pseudo-code, how does the compiler handle this?
fcn_call (A, B, fcn_call2 (A2, B2).fortran_vec (), C);
line2;
If fcn_call2 returns a Matrix object for which we then call fortran_vec() I
don't think the compiler arranges to call the destructor until line2 is
reached. Since we don't need the results beyond the execution of fcn_call I
believe this is okay.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?50105>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/