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: 5541 Reporter: gerd Status: resolved (set by @xavierleroy on 2012-03-16T09:12:37Z) Resolution: suspended Priority: normal Severity: tweak Version: 3.12.1 Category: back end (clambda to assembly) Has duplicate:#4808#5592 Monitored by:ronan.lehy@gmail.com mehdi dario Camarade_Tux @hcarty@Chris00
Bug description
I just observed that min/max are not inlined. This prevents that further optimizations on the comparison operator can be applied - min/max always use compare_val.
Maybe compiling Pervasives with a slightly increased inlining limit already solves the problem.
Steps to reproduce
ocamlobjinfo /pervasives.cmx
The text was updated successfully, but these errors were encountered:
Unfortunately, type-based specialization of comparisons takes place before inlining. In other words, even if min & max were inlined, they would still use the generic comparison operator. That's one of the several weaknesses of the OCaml inliner. I'm not expecting a solution soon, which is why I'm putting this PR in "suspended" state.
Original bug ID: 5541
Reporter: gerd
Status: resolved (set by @xavierleroy on 2012-03-16T09:12:37Z)
Resolution: suspended
Priority: normal
Severity: tweak
Version: 3.12.1
Category: back end (clambda to assembly)
Has duplicate: #4808 #5592
Monitored by: ronan.lehy@gmail.com mehdi dario Camarade_Tux @hcarty @Chris00
Bug description
I just observed that min/max are not inlined. This prevents that further optimizations on the comparison operator can be applied - min/max always use compare_val.
Maybe compiling Pervasives with a slightly increased inlining limit already solves the problem.
Steps to reproduce
ocamlobjinfo /pervasives.cmx
The text was updated successfully, but these errors were encountered: