| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0004454 | OCaml | OCaml backend (code generation) | public | 2007-11-22 16:38 | 2012-12-14 09:32 |
|
| Reporter | frisch | |
| Assigned To | | |
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | acknowledged | Resolution | open | |
| Platform | | OS | | OS Version | |
| Product Version | | |
| Target Version | | Fixed in Version | | |
|
| Summary | 0004454: Better control over cross-module optimizations |
| Description | It should be possible to have finer control over cross-module optimizations as performed by ocamlopt. Typical motivations:
1. Speed up the edit-compile-run cycle (bytecode is not always an option).
2. Allow .cmxs plugins to be used in several different applications sharing only some interfaces.
Possible ideas:
1. When a module is compiled by ocamlopt, a special option asks ocamlopt no to produce cross-module info for the resulting .cmx.
2. A different set of search directories to look for .cmx files.
3. Put cross-module info into .cmxa and let ocamlopt use .cmxa at compile-time
to perform optimizations.
4. Explicitly allow/disallow ocamlopt (with command line options) to use cross-module optimizations for some modules.
|
| Tags | No tags attached. |
|
| Attached Files | |
|
Relationships 
Relationships 