octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #62409] [octave forge] (image) BIST errors on


From: Hartmut
Subject: [Octave-bug-tracker] [bug #62409] [octave forge] (image) BIST errors on 32-bit
Date: Fri, 6 May 2022 14:24:26 -0400 (EDT)

Follow-up Comment #2, bug #62409 (project octave):

If I see this right in the buildbot logs, then the two already mentioned
failing tests of "imerode.cc-tst" are the only two tests failing, at least in
the current image package 2.14.

Question 1: What is the largest number of elements that an Octave array of
type "double" is (roughly) allowed to have when octave_idx_type is 32-bit?
When I calculate 2^32 I get 4.3e9, is this the correct maximum number of array
elements?

Currently in theses two tests the array a has roughly 1.5e6 elements and the
array b has rougly 5.1e6 elements. Are these already too many, or does the
index overflow only happen during the calculations (of imerode/imdilate.cc,
convn or colfilt)?

Question 2: Would I be able to reproduce this error when using the
"octave-7.1.0-w32-installer.exe" under Windows? Or is this 32-bit indexing
something different?


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62409>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]