Online Developer Meeting (2021-11-23): Difference between revisions

Jump to navigation Jump to search
m
 
(4 intermediate revisions by 2 users not shown)
Line 21: Line 21:
=== MXE Octave merge strategy ===
=== MXE Octave merge strategy ===


* When should the release branch of MXE Octave be merged to the default branch?
* When should the default branch of MXE Octave be merged to the release branch?
** Around the same time as the merge of the default branch of Octave to its stable branch.
* Which branches should the buildbots use in the pre-release phase? Different for jwe's buildbots and octave.space?
* Which branches should the buildbots use in the pre-release phase? Different for jwe's buildbots and octave.space?
** Keep them running like they are. Evaluate if buildbot failures need action in the transition period before the major release.


=== UCRT version of Octave? ===
=== UCRT version of Octave? ===


* Should we distribute an UCRT version of Octave for Windows?
* Should we distribute an UCRT version of Octave for Windows?
** Probably changes inside Octave necessary as well.
** No big opposition to adding new versions if it doesn't become too many and they add value.
** Probably changes inside Octave necessary as well. Long time project. Maybe for Octave 8 (or later).
** See: [https://octave.discourse.group/t/1821 Windows, UTF-8, and UCRT - yet another variant of Octave on Windows?]
** See: [https://octave.discourse.group/t/1821 Windows, UTF-8, and UCRT - yet another variant of Octave on Windows?]


Line 45: Line 48:
* OpenMP parallelization for trivial cases (e.g. initialize matrix with constant)?
* OpenMP parallelization for trivial cases (e.g. initialize matrix with constant)?
** Ensure thread safeness of Array classes (especially GUI-interpreter communication)
** Ensure thread safeness of Array classes (especially GUI-interpreter communication)
* Other performance improvments:
** Maybe based on <code>std:shared_ptr</code>? But they aren't guaranteed to be thread-safe by design either.
** Idea: memory pools bug {{bug|57321}}
** Eliminate <code>mutable</code> class data.
** Idea: static_cast vs. dynamic_case bug {{bug|???}}
* Other performance improvements:
** Idea: memory pools: bug {{bug|57321}}
** Idea: static_cast vs. dynamic_cast: patch {{patch|10139}}
** General remark: Prefer standard features instead of "reinventing the wheel" by implementing intricate optimizations.


== Previous topics ==
== Previous topics ==
209

edits

Navigation menu