diff options
author | Mohammad Akhlaghi <mohammad@akhlaghi.org> | 2020-06-01 06:29:52 +0100 |
---|---|---|
committer | Mohammad Akhlaghi <mohammad@akhlaghi.org> | 2020-06-01 06:29:52 +0100 |
commit | 7d6ee8ce978a24cd2c796734f358dd8cd49da553 (patch) | |
tree | e51fdb90798371378cbf81cadda72095ac39b9a0 /reproduce/software/patches/valgrind-3.15.0-mpi-fix1.patch | |
parent | 3db3859a2d5615ad9d2e2fb7361bd3cc569475a9 (diff) |
Minor edits to clarify some of the previous corrections
Boud's point about a "random reader" not being a good example case was
correct. But "user" also gives it a software perspective that is ofcourse
not wrong, its can just be confusing. So I thought of changing it to
"interested reader".
In the part about the C-library dependency of high-level software, from
Boud's correction, I found out that it is very hard to convey what I wanted
to say (that separating errors due to C-library implementation and
measurement errors will be easy, because they should be on much different
scales). But I then corrected it to give it a slightly better tone while
mentioning the same thing: that with Maneage we can now accurately measure
the effect of the C library.
Diffstat (limited to 'reproduce/software/patches/valgrind-3.15.0-mpi-fix1.patch')
0 files changed, 0 insertions, 0 deletions