From 9abbb0503c437c1fa0977f4b34fdd5d91026ea36 Mon Sep 17 00:00:00 2001 From: Justin Ethier Date: Fri, 16 Jun 2017 03:47:59 -0400 Subject: [PATCH] Revisions --- ...5-Using-the-C-Profiler-and-Debugger-with-Cyclone-Scheme.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_posts/2017-06-05-Using-the-C-Profiler-and-Debugger-with-Cyclone-Scheme.md b/_posts/2017-06-05-Using-the-C-Profiler-and-Debugger-with-Cyclone-Scheme.md index 75272c1b..dc3a939a 100644 --- a/_posts/2017-06-05-Using-the-C-Profiler-and-Debugger-with-Cyclone-Scheme.md +++ b/_posts/2017-06-05-Using-the-C-Profiler-and-Debugger-with-Cyclone-Scheme.md @@ -52,7 +52,7 @@ Then we run `gprof` to create a report: gmon.out inputs outputs tail tail.c tail.o tail.scm [justin@justin-pc Cyclone]$ gprof ./tail gmon.out > report.txt -Let's examine the start of `report.txt` to see the functions that are taking up the most of the program's runtime: +Let's examine the start of `report.txt` to see the functions that account for most of the program's runtime: Flat profile: @@ -192,4 +192,4 @@ After rebuilding with this fix we can re-run the tail benchmark: user 0m0.540s sys 0m0.187s -Whoa! Remember how the older code took over 32 seconds to finish? Now it finishes in less than a second. Not bad. +Whoa! Remember how the older code took over 32 seconds to finish? Now it finishes in less than a second. [Not bad](http://ecraven.github.io/r7rs-benchmarks/benchmark.html).