22< html >
33< head >
44 < meta charset ="utf-8 " />
5- < title > Using HerbGrind </ title >
5+ < title > Using Herbgrind </ title >
66 < base href ="../.. "/>
77 < link rel ='stylesheet ' type ='text/css ' href ='main.css '>
88</ head >
99< body >
1010 < header >
1111 < a href =". "> < img class ="logo " src ="logo.png " /> </ a >
12- < h1 > Using HerbGrind </ h1 >
12+ < h1 > Using Herbgrind </ h1 >
1313 </ header >
1414
1515 < p >
16- < a href =". "> HerbGrind </ a > analyzes binaries to find inaccurate
16+ < a href =". "> Herbgrind </ a > analyzes binaries to find inaccurate
1717 floating point expressions. The binaries can come from anywhere—C
1818 source, Fortran source, even unknown origins. This tutorial
19- runs HerbGrind on the benchmark programs that HerbGrind ships with.
19+ runs Herbgrind on the benchmark programs that Herbgrind ships with.
2020 </ p >
2121
2222 < h2 > Compiling the benchmark program</ h2 >
2323
2424 < p >
25- HerbGrind ships test binaries in its < code > bench/</ code >
25+ Herbgrind ships test binaries in its < code > bench/</ code >
2626 directory. You can build them with:
2727 </ p >
2828
2929 < pre > make -C bench all</ pre >
3030
3131 < p >
3232 Let's analyze the < code > diff-roots-simple.out</ code > binary that
33- you just compiled. Run HerbGrind on that binary with:
33+ you just compiled. Run Herbgrind on that binary with:
3434 </ p >
3535
3636 < pre > valgrind/herbgrind-install/bin/valgrind --tool=herbgrind bench/diff-roots-simple.out</ pre >
@@ -39,7 +39,7 @@ <h2>Compiling the benchmark program</h2>
3939 This should produce output that looks like this:
4040 </ p >
4141
42- < pre > ==16725== HerbGrind , a valgrind tool for Herbie
42+ < pre > ==16725== Herbgrind , a valgrind tool for Herbie
4343==16725==
4444==16725== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info
4545==16725== Command: bench/diff-roots-simple.out
@@ -49,7 +49,7 @@ <h2>Compiling the benchmark program</h2>
4949Writing report out to bench/diff-roots-simple.out-errors.gh</ pre >
5050
5151 < p > The printed value, < code > 1.578592e-07</ code > , is printed by
52- the < code > diff-roots-simple.out</ code > binary. HerbGrind writes its
52+ the < code > diff-roots-simple.out</ code > binary. Herbgrind writes its
5353 results to the named
5454 file, < code > bench/diff-roots-simple.out-errors.gh</ code > . This file
5555 contains one record for each operation; the only operation found
@@ -72,7 +72,7 @@ <h2>Compiling the benchmark program</h2>
7272 < pre > y = sqrt(x + 1) - sqrt(x);</ pre >
7373
7474 < p >
75- Since this line of code is run only once, HerbGrind doesn't know
75+ Since this line of code is run only once, Herbgrind doesn't know
7676 that < code > x</ code > is intended to be a variable, and instead
7777 inlines its value.
7878 </ p >
@@ -82,13 +82,13 @@ <h2>Compiling the benchmark program</h2>
8282 inaccurate computation: 43.1 bits of error over 1 instance of computing that expression.
8383 </ p >
8484
85- < h2 > Turning HerbGrind on and off</ h2 >
85+ < h2 > Turning Herbgrind on and off</ h2 >
8686
8787 < p >
88- While running on < code > diff-roots-simple.out</ code > , HerbGrind
88+ While running on < code > diff-roots-simple.out</ code > , Herbgrind
8989 found inaccurate computations not only
9090 in < code > diff-roots-simple.out</ code > but also in several GNU
91- library calls. HerbGrind has a feature to avoid tracking floating
91+ library calls. Herbgrind has a feature to avoid tracking floating
9292 point operations in libraries and other code not within your
9393 control by adding instrumentation to your source code.
9494 </ p >
@@ -106,8 +106,8 @@ <h2>Turning HerbGrind on and off</h2>
106106// cleanup code ...</ pre >
107107
108108 < p > The < code > diff-roots-simple.c</ code > example does this on lines
109- 11 and 13. You can then run HerbGrind with
110- the < code > --start-off</ code > flag, which tells HerbGrind not to
109+ 11 and 13. You can then run Herbgrind with
110+ the < code > --start-off</ code > flag, which tells Herbgrind not to
111111 begin analyzing floating point operations until it sees
112112 a < code > HERBGRIND_BEGIN()</ code > region:
113113 </ p >
@@ -123,8 +123,8 @@ <h2>Turning HerbGrind on and off</h2>
123123 < p >
124124 The < code > HERBGRIND_BEGIN()</ code > /< code > HERBGRIND_END()</ code >
125125 regions can be sprinkled anywhere in your source code; it's common
126- to use them to start HerbGrind only after initializing your
127- program and before cleaning up and outputting results. HerbGrind
126+ to use them to start Herbgrind only after initializing your
127+ program and before cleaning up and outputting results. Herbgrind
128128 can be turned on and off multiple times.
129129 </ p >
130130
0 commit comments