assembly labels loop on huge generated .ml files #4869
Assignees
Labels
Comments
|
Comment author: @xavierleroy Tentative fix in SVN trunk, commit 11887. Tested only on AMD64/Linux so far. |
|
Comment author: meurer Confirmed to work with ARM/Linux. |
|
Comment author: meyer I bumped on it also just few days ago at work when compiling 200K of mechanically generated OCaml code, I'll validate it today and update the issue. Thank you for fixing this! |
|
Comment author: meyer Indeed, I tried with the project that stopped compiling and it works flawlessly. Sorry to keep you waited. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Original bug ID: 4869
Reporter: louis
Assigned to: @xavierleroy
Status: closed (set by @xavierleroy on 2012-09-25T18:07:21Z)
Resolution: fixed
Priority: normal
Severity: minor
Version: 3.11.1
Fixed in version: 3.13.0+dev
Category: ~DO NOT USE (was: OCaml general)
Bug description
native code generation uses a barrier at 100000 for the generation of asm labels, at least on i386 and amd64 (haven't tried others). This only happens when using ocaml on very huge generated code, but there doesn't seem to be a good reason to enforce this limitation (except, perhaps, readability of the asm); besides, ocaml doesn't complain but generates invalid assembly code.
Additional information
here is a possible patch that replaces the barrier at 100000 to max_int/2 : it's not pretty but solves the issue alright
File attachments
The text was updated successfully, but these errors were encountered: