254
edits
(→Release process of Octave 7.1: Mark bug as fixed.) |
|||
Line 8: | Line 8: | ||
=== Release process of Octave 7.1 === | === Release process of Octave 7.1 === | ||
* Blocking issues: | * Blocking issues: 8 open bugs targeting 7.0.90, 3 marked as "ready for test" (see [https://octave.space/savannah/# Savannah overview on octave.space]) | ||
* Good progress on some of the blocking issues by jwe. Most important remaining ones: | * Good progress on some of the blocking issues by jwe. Most important remaining ones: | ||
** bug {{bug|61788}}: arrays of type int16 contain wrong numbers | ** bug {{bug|61788}}: arrays of type int16 contain wrong numbers | ||
Line 14: | Line 14: | ||
** bug {{bug|61813}}: memory management bug when calling MEX that returns an output | ** bug {{bug|61813}}: memory management bug when calling MEX that returns an output | ||
*** @jwe check in a fix that will also revert to copying data in the .mex interface (less efficient, but also the way it has always been done until now) unless Octave is compiled with C++17 pmr. | *** @jwe check in a fix that will also revert to copying data in the .mex interface (less efficient, but also the way it has always been done until now) unless Octave is compiled with C++17 pmr. | ||
*** This also avoids the <code>malloc</code>-<code>operator delete[]</code> mismatch. | |||
*** Confirmed fixed now. | |||
** bug {{bug|61821}}: segfault using tree_parameter_list in oct file | ** bug {{bug|61821}}: segfault using tree_parameter_list in oct file | ||
*** Lower priority, only 32-bit (only on Windows?). Maybe a compiler bug? Probably not a blocker. | *** Lower priority, only 32-bit (only on Windows?). Maybe a compiler bug? Probably not a blocker. |