wrey75
commented
8 years ago [correct me if I'm wrong, but I'm guessing the original reporter is @wrey75]
I think you're wrong ;-)
I don't remember having worked with ocamlbuild.
Best regards, William Rey. Webmaster de www.koikonfait.com
Envoyé de mon téléphone portable.
Le 18 avr. 2016 à 14:02, Damien Doligez notifications@github.com a écrit :
PR transferred from http://caml.inria.fr/mantis/view.php?id=6789 [correct me if I'm wrong, but I'm guessing the original reporter is @wrey75]
in ocamlbuild documentation, the section "18.3.20 Debugging byte code and profiling native code" could be a bit clearer.
"The preferred way of compiling code suitable for debugging with ocamldebug or profiling native code with ocamlprof is to use the appropriate target extensions, .d.byte for debugging or .p.native." => "To compile code suitable for debugging with ocamldebug, use the target extension .d.byte. To compile code suitable for profiling with gprof, use the target extension .p.native"
"Please note that the byte-code profiler works in a wholly different way and is not supported by ocamlbuild." => "Please note that the byte-code profiler ocamlprof works in a wholly different way and is not supported by ocamlbuild."
Furthermore, ocamlprof can be replaced if I have well understood by gprof -A. So it would be nice to add to the last comment : "[...] is not supported by ocamlbuild. Use if possible the target .p.native along with gprof -A to insert information in source code". But in this case, "true:debug" must be added in order for gprof -A to work. So I was wondering if ".p.profile" should also add debug tag...
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub
dbuenzli
PR transferred from http://caml.inria.fr/mantis/view.php?id=6789 [correct me if I'm wrong, but I'm guessing the original reporter is @wrey75]
in ocamlbuild documentation, the section "18.3.20 Debugging byte code and profiling native code" could be a bit clearer.
"The preferred way of compiling code suitable for debugging with ocamldebug or profiling native code with ocamlprof is to use the appropriate target extensions, .d.byte for debugging or .p.native." => "To compile code suitable for debugging with ocamldebug, use the target extension .d.byte. To compile code suitable for profiling with gprof, use the target extension .p.native"
"Please note that the byte-code profiler works in a wholly different way and is not supported by ocamlbuild." => "Please note that the byte-code profiler ocamlprof works in a wholly different way and is not supported by ocamlbuild."
Furthermore, ocamlprof can be replaced if I have well understood by gprof -A. So it would be nice to add to the last comment : "[...] is not supported by ocamlbuild. Use if possible the target .p.native along with gprof -A to insert information in source code". But in this case, "true:debug" must be added in order for gprof -A to work. So I was wondering if ".p.profile" should also add debug tag...