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: 4454 Reporter:@alainfrisch Assigned to:@mshinwell Status: resolved (set by @mshinwell on 2016-12-06T22:09:27Z) Resolution: fixed Priority: normal Severity: feature Category: back end (clambda to assembly) Related to:#6389 Monitored by:@bobzhang@gasche@ygrek "Julien Signoles" @hcarty
Bug description
It should be possible to have finer control over cross-module optimizations as performed by ocamlopt. Typical motivations:
Speed up the edit-compile-run cycle (bytecode is not always an option).
Allow .cmxs plugins to be used in several different applications sharing only some interfaces.
Possible ideas:
When a module is compiled by ocamlopt, a special option asks ocamlopt no to produce cross-module info for the resulting .cmx.
A different set of search directories to look for .cmx files.
Put cross-module info into .cmxa and let ocamlopt use .cmxa at compile-time
to perform optimizations.
Explicitly allow/disallow ocamlopt (with command line options) to use cross-module optimizations for some modules.
The text was updated successfully, but these errors were encountered:
Original bug ID: 4454
Reporter: @alainfrisch
Assigned to: @mshinwell
Status: resolved (set by @mshinwell on 2016-12-06T22:09:27Z)
Resolution: fixed
Priority: normal
Severity: feature
Category: back end (clambda to assembly)
Related to: #6389
Monitored by: @bobzhang @gasche @ygrek "Julien Signoles" @hcarty
Bug description
It should be possible to have finer control over cross-module optimizations as performed by ocamlopt. Typical motivations:
Possible ideas:
to perform optimizations.
The text was updated successfully, but these errors were encountered: