You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 5115 Reporter:@damiendoligez Assigned to:@xavierleroy Status: closed (set by @xavierleroy on 2012-03-24T14:01:44Z) Resolution: fixed Priority: normal Severity: minor OS: Windows OS Version: 64-bit Version: 3.12.0 Fixed in version: 3.12.1+dev Category: ~DO NOT USE (was: OCaml general) Monitored by:@alainfrisch
Bug description
In the 64-bit MSVC version, output-value does the wrong thing on native ints and makes them unreadable by 32-bit versions of OCaml.
Also, if a 64-bit version of OCaml compiles a program with a large nativeint constant, the resulting bytecode will crash the 32-bit versions because they try to raise an exception before the global constants are initialized.
Steps to reproduce
Bootstrap with MSVC in 64-bit mode and try to use the resulting ocamlc, e.g. under cygwin -> crash
The text was updated successfully, but these errors were encountered:
Original bug ID: 5115
Reporter: @damiendoligez
Assigned to: @xavierleroy
Status: closed (set by @xavierleroy on 2012-03-24T14:01:44Z)
Resolution: fixed
Priority: normal
Severity: minor
OS: Windows
OS Version: 64-bit
Version: 3.12.0
Fixed in version: 3.12.1+dev
Category: ~DO NOT USE (was: OCaml general)
Monitored by: @alainfrisch
Bug description
In the 64-bit MSVC version, output-value does the wrong thing on native ints and makes them unreadable by 32-bit versions of OCaml.
Also, if a 64-bit version of OCaml compiles a program with a large nativeint constant, the resulting bytecode will crash the 32-bit versions because they try to raise an exception before the global constants are initialized.
Steps to reproduce
Bootstrap with MSVC in 64-bit mode and try to use the resulting ocamlc, e.g. under cygwin -> crash
The text was updated successfully, but these errors were encountered: