bugGNU Octave - Bugs: bug #43525, mxe-octave: compile with OpenBLAS...

 
 

bug #43525: mxe-octave: compile with OpenBLAS with OMP enabled

Submitter:  Ceral Paquet <octavebugs>
Submitted:  Tue 04 Nov 2014 10:38:58 AM UTC
 
Category:  Configuration and Build System Severity:  1 - Wish
Priority:  5 - Normal Item Group:  Feature Request
Status:  Fixed Assigned to:  lostbard
Originator Name:  Open/Closed:  * Closed
Release:  * 3.8.2 Operating System:  * Microsoft Windows
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       

 

( Jump to the original submission )

Thu 19 Feb 2015 01:40:12 AM UTC, comment #6: 

I ran in win7 with no issues. But I also havent had any issues with printing either ...

John Donoghue <lostbard>
Project Member
Wed 18 Feb 2015 07:15:16 PM UTC, comment #5: 

Can this bug be closed now?  I've built MXE-Octave with the new patch in place and it appears to work.  I inverted a random 100x100 matrix.  I also changed the environment variable OPENBLAS_NUM_THREADS to 2 and ran the CLI version of Octave and it appeared to work.

I tried to run _run_test_suite_ but I got a segmentation violation which I will report as a new bug because I don't think it is related to this.

Rik <rik5>
Project Administrator
Tue 17 Feb 2015 07:00:33 PM UTC, comment #4: 
John Donoghue <lostbard>
Project Member
Fri 30 Jan 2015 04:23:58 PM UTC, comment #3: 

Updating summary based on the primary request.

Mike Miller <mtmiller>
Project Administrator
Tue 04 Nov 2014 06:06:34 PM UTC, comment #2: 

Looking through init.c from OpenBLAS, if it doesn't find any relevant environment variables (including OMP_NUM_THREADS) then it defaults to using all the cores.

Ceral Paquet <octavebugs>
Tue 04 Nov 2014 02:48:33 PM UTC, comment #1: 

If threading is enabled, what should the default be for OPENBLAS_NUM_THREADS?  What does openblas use if that environment variable is not set?

You are welcome to build Octave with whatever options you choose, but there are still a number of problems with 64-bit indexing so --enable-64 should not yet be made the default.

John W. Eaton <jwe>
Project Administrator
Tue 04 Nov 2014 10:38:58 AM UTC, original submission:  

I noticed when running the Windows MXE builds that only a single thread is used even when BLAS-heavy routines. Looking at the MXE make file openblas.mk indicates USE_THREAD=0 is the default.

Would it be possible to turn USE_THREAD=1 and then let users specify OPENBLAS_NUM_THREADS as an environment variable?

Also, would it be possible to configure the Windows build to use --enable-64?

Ceral Paquet <octavebugs>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rik5 (Posted a comment)
  • -email is unavailable- added by lostbard (Updated the item)
  • -email is unavailable- added by mtmiller (Posted a comment)
  • -email is unavailable- added by jwe (Posted a comment)
  • -email is unavailable- added by octavebugs (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only project members can vote.

     

     

     

     

    Follow 9 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2015-02-20 lostbard StatusReady For Test Fixed
        Open/ClosedOpen Closed
    2015-02-17 lostbard StatusIn Progress Ready For Test
    2015-02-17 lostbard StatusNone In Progress
        Assigned toNone lostbard
    2015-01-30 mtmiller CategoryNone Configuration and Build System
        Severity3 - Normal 1 - Wish
        Item GroupNone Feature Request
        SummaryMXE defaults for Windows builds mxe-octave: compile with OpenBLAS with OMP enabled

    Back to the top


    Powered by Savane 3.9