Re: Unofficial octave 4.4.0 Windows binary with large arrays

[Tatsuro MATSUOKA]

> From: mmuetzel > To: address@hidden
> Cc: 
> Date: 2018/5/6, Sun 18:28
> Subject: Re: Unofficial octave 4.4.0 Windows binary with large arrays
> 
> One of the flags in __octave_config_info__ ("config_opts") when called 
> in the
> official Octave 4.4.0 (Windows installer 64-bit) is '--disable-64'

Thanks for information.

.
> For my own cross-compiled versions there is '--enable-64' even if I 
> don't
> specifically configure mxe-octave with --enable-64. The configure flags I
> use for mxe-octave are (default Octave that is):
> ./configure --enable-devel-tools --enable-windows-64 --enable-octave=default
> --enable-binary-packages
> --with-pkg-dir=/home/markus/Repositories/Octave/mxe-octave-pkg --with-ccache
> --disable-system-opengl

There are differences between stable (4.4.0) and defalut (4.5.0).

For 4.4 as you wrote. BLAS etc libraries. should be prepared with 64 bit index.
For mxe-octave for stable (4.4)  --enable-fortran-int64 ineviably required 
for 64 bit index build for stable

For 4,5, one can use 64 bit index evenif BLAS etc. are built with 32bit index.
Thus  --enable-fortran-int64 is not required for default (4.5) mxe build.


> Is it possible to somehow determine which flags where used to configure
> mxe-octave for the official installer?


--enable64 --enable-windows64 and --enable-fortran-int64 for stable branch.
 


> And still: Is it intentional that the official Windows 64-bit versions use
> 32-bit indexing?
> 


Perhaps 64 index for 64 bit binary will be default in the next major release.
I am not a developer but a one of heavy users.  
I suspect that windows binary this release is built with 32 bit index is 
intentional.

Developer will make a definite rely.

Tatsuro