[Octave-bug-tracker] [bug #46533] numel() returns negative values for large diagonal matrices

[Nicholas Jankowski]

Follow-up Comment #1, bug #46533 (project octave):

a quick check in both octave and matlab shows that numel output is a double.
so is the issue just that the row*column step is starting with uint32 numbers
and trying to keeping it that way? knowing that numel should be able to get
bigger than the index limit, can numel be patched to internally class change
to double before whatever arithmetic is causing a problem so this becomes a
non-issue? it's coming out as a double... does it matter where the class
change happens?

(I did play with matlab 2015b and created a 10000x10000x100x100 array of
logicals.  numel(x) output 1e11 without error)

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?46533>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/