[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #47554] logm(rand(i)) : i>=130 gives segfault
From: |
Philip Nienhuis |
Subject: |
[Octave-bug-tracker] [bug #47554] logm(rand(i)) : i>=130 gives segfault on mxe-octave 64bit (openblas issue) |
Date: |
Mon, 28 Mar 2016 08:59:53 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0 SeaMonkey/2.38 |
Follow-up Comment #1, bug #47554 (project octave):
It works fine with the 32-bit version (using openblas) from ftp.gnu.org:
>> tic; a = logm (rand(1000)); toc
Elapsed time is 53.309 seconds.
(where cpu time in task manager = 39 seconds).
I saw only 25% CPU load, I'm sure I had openblas selected at install time.
Indeed libblas.dll's size in /bin equals that of libopenblas.dll)
I have no home-built 64-bit 4.0.1 version, I'll see if I can make one today
and try this again.
With a development 4.1.0+ cross-build, also invoking openblas, I cannot
reproduce it here either. It was configured with:
--enable-windows-64 --enable-devel-tools --enable-binary-packages
--enable-octave=default
and an octave-4.1.0+ "make dist" based on 6187f1d2ca13 "zip.m: Restore
processing of wildcards ...."
Octave-4.1.0+ seems a bit faster:
>> tic; a = logm (rand(1000)); toc
Elapsed time is 44.1555 seconds.
(CPU time according to Task Manager 30 secs. CPU load 75 % for a while)
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?47554>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #47554] logm(rand(i)) : i>=130 gives segfault on mxe-octave 64bit (openblas issue), Tatsuro MATSUOKA, 2016/03/28
- [Octave-bug-tracker] [bug #47554] logm(rand(i)) : i>=130 gives segfault on mxe-octave 64bit (openblas issue),
Philip Nienhuis <=
- [Octave-bug-tracker] [bug #47554] logm(rand(i)) : i>=130 gives segfault on mxe-octave 64bit (openblas issue), Tatsuro MATSUOKA, 2016/03/28
- [Octave-bug-tracker] [bug #47554] logm(rand(i)) : i>=130 gives segfault on mxe-octave 64bit (openblas issue), Philip Nienhuis, 2016/03/28
- [Octave-bug-tracker] [bug #47554] logm(rand(i)) : i>=130 gives segfault on mxe-octave 64bit (openblas issue), Mike Miller, 2016/03/28
- [Octave-bug-tracker] [bug #47554] logm(rand(i)) : i>=130 gives segfault on mxe-octave 64bit (openblas issue), Philip Nienhuis, 2016/03/28
- [Octave-bug-tracker] [bug #47554] logm(rand(i)) : i>=130 gives segfault on mxe-octave 64bit (openblas issue), John Donoghue, 2016/03/29
- [Octave-bug-tracker] [bug #47554] logm(rand(i)) : i>=130 gives segfault on mxe-octave 64bit (openblas issue), John Donoghue, 2016/03/29
- [Octave-bug-tracker] [bug #47554] logm(rand(i)) : i>=130 gives segfault on mxe-octave 64bit (openblas issue), John Donoghue, 2016/03/29
- [Octave-bug-tracker] [bug #47554] logm(rand(i)) : i>=130 gives segfault on mxe-octave 64bit (openblas issue), John Donoghue, 2016/03/29
- [Octave-bug-tracker] [bug #47554] logm(rand(i)) : i>=130 gives segfault on mxe-octave 64bit (openblas issue), Tatsuro MATSUOKA, 2016/03/29
- [Octave-bug-tracker] [bug #47554] logm(rand(i)) : i>=130 gives segfault on mxe-octave 64bit (openblas issue), John Donoghue, 2016/03/30