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

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

[Octave-bug-tracker] [bug #58957] [octave forge] (sparsersb) Failure to


From: dezperado
Subject: [Octave-bug-tracker] [bug #58957] [octave forge] (sparsersb) Failure to install and crash in function
Date: Fri, 30 Oct 2020 09:09:01 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.149 Safari/537.36

Follow-up Comment #55, bug #58957 (project octave):

Hi Markus,

> Would it instead (or additionally) be possible for the function to emit an
error if the second input argument is "render"?
If you guys give me the #ifdef-based recipe to do that, I'd do it or let's to
it straight away.

> I understand if you don't want to make that change in your released version
because it seems to be a Windows-only bug.
Seems so, but one shall dig further, and I appreciate your help.

> But we could apply a changeset to your sources in MXE Octave.
It would be best if you could provide a changeset that applies on top of the
latest released version.
Sure.

> Please, let me know if you don't agree.
I think a practical short-term solution would be to either remove the test or
even block the 'render' demos or the render functionality on windows.

> If you don't want to spend your time on this, please let me now as well, and
I can try and have a look myself.
Hmmm yes but we need a small reproducer program. I can write that relatively
easily, but you would have to compile and run it under the Windows environment
where sparsersb crashes. And you would follow it with gdb. In the best
(clearest) case it will crash. But it might not. Is that OK with you ? If yes,
I take an hour aside and I prepare that reproducer.  


In all this, in let me remark again: 


That "render" functionality is only to get the "recursive sparse blocks"
rendering of matrices represented in sparsersb. Its only use is to produce EPS
plots to display how sparsersb arranges submatrices. I use it when I do
presentation of sparsersb/librsb. Or sure, to debug librsb or sparsersb.

The 99.9% of octave-sparsersb users would only use it in order to squeeze
multicore performance when multiplying sparse matrices by vectors or
multi-vectors.
And if somebody is not getting speedup by using sparsersb (because e.g. using
too small a matrix), than I see no reason of using sparsersb.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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