Bigarray dimensions too limited on 64bit architectures #4457
Assignees
Labels
Comments
|
Comment author: @xavierleroy I agree this limitation should be lifted. The main reason for it was to simplify marshalling when a bigarray is marshalled on a 64-bit platform, then read back on a 32-bit platform. But it should be possible to change the marshalling format to support 64-bit dimensions, yet remain compatible with the current format. |
|
Comment author: @xavierleroy Removed the limitation on bigarray dimensions in CVS trunk. The concern with marshalling was a non-issue: output_value refuses to produce marshalled data >= 4 Gb anyway, which is the case for any bigarray having one dimension >= 2^32. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Original bug ID: 4457
Reporter: @mmottl
Assigned to: @xavierleroy
Status: closed (set by @xavierleroy on 2008-01-04T09:59:17Z)
Resolution: fixed
Priority: normal
Severity: minor
Version: 3.10+dev
Category: ~DO NOT USE (was: OCaml general)
Related to: #5511
Monitored by: jm @dbuenzli @Chris00 @mmottl
Bug description
The following expression
Bigarray.Array1.create Bigarray.char Bigarray.c_layout 3_000_000_000;;
when evaluated on a 64bit architecture raises this exception:
Exception: Invalid_argument "Bigarray.create: negative dimension".
This seems misleading, because this is not a negative dimension. But even worse, it is an unnecessary limitation on 64bit architectures that nowadays may well have sufficient memory - and need it for demanding applications.
Could you please remove this limitation on platforms that don't require it? - Thanks!
The text was updated successfully, but these errors were encountered: