Errata
The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
Version | Location | Description | Submitted by | Date submitted |
---|---|---|---|---|
1 1st paragraph |
There are no page numbers for my copy of this book. The error is in the 1st paragraph of "Chapter 1. An Overview of Optimization". It's a typo for "that": |
Paul evans | Mar 16, 2015 | |
7 Use a Better Compiler, Use Your Compiler Better |
There are no page numbers for my copy of this book. The problem is with the "Chapter 1. Summary of Strategies for Optimizng C++ Code: Use a Better Compiler, Use Your Compiler Better" section. |
Paul Evans | Mar 17, 2015 | |
7 Use a Better Compiler, Use Your Compiler Better |
There are no page numbers for my copy of this book. The problem is with the "Chapter 1. Summary of Strategies for Optimizng C++ Code: Use a Better Compiler, Use Your Compiler Better" section. |
Paul Evans | Mar 17, 2015 | |
13 bootom |
There are no page numbers for my copy of this book. The error is in the 1st paragraph of "Chapter 1. An Overview of Optimization. Summary" |
Paul Evans | Mar 18, 2015 | |
17 1st paragraph |
There are no page numbers for my copy of this book. The error is in the 1st paragraph of the Memory is Not Accessed in Bytes section of Chapter 2. |
Paul Evans | Mar 18, 2015 | |
Page 18 Second paragraph |
The text includes a symlink to "#chapter-measuring-performance" in two places rather than spelling out the name of the chapter. |
Anonymous | Sep 30, 2015 | |
Page 19 First paragraph |
The text contains a symlink to "#chapter-measuring-performance" rather than spelling out the title. |
Anonymous | Sep 30, 2015 | |
Page 20 Fifth, sixth and seventh paragraphs |
The text contains symlinks to "#chapter-strings" or "???". These should be spelled out. |
Anonymous | Sep 30, 2015 | |
Page 20 2nd paragraph of "Memory Words Have a Big End and a Little End" |
Little-Endianness and Big-Endianness are mixed-up in the example: |
Anonymous | Sep 06, 2016 | |
25 last paragraph |
There are no page numbers for my copy of this book. The error is in the last paragraph of the C++ Tells Lies Too section of Chapter 2. |
Paul Evans | Mar 19, 2015 | |
Printed | Page 27 3rd paragraph |
On this episode, "Isaac Newton measured the gravitational constant by timing falling objects against his heartbeat." I think author is misunderstanding by "Galileo Galilei measured the isochrony of the pendulum by his heartbeat." Henry Cavendish succeeded measure of gravitational constant in 1798, 70 years after Newton's death. :-) |
Yukitoshi Fujimura | Jan 16, 2017 |
28 1st paragraph |
There are no page numbers for my copy of this book. The error is in the 1st paragraph of "Chapter 3. Measure Performance" |
Paul Evans | Mar 19, 2015 | |
Page 33 3rd paragraph |
"After a conditional branch instruction, eexecution continues" - note eexecution (sic). |
Jason | Sep 23, 2015 | |
Page 35 1st |
"In such a situation, improving |
Nathan Beasley | Mar 16, 2016 | |
Page 76 Eliminate Pointer Dereference Using Iterators |
"Eliminate Pointer Dereference Using Iterators" describes the efficiency gained by using iterators as "avoiding pointer dereference". In reality most iterators are actually implemented as pointers. The efficiency gained by iterators is not in avoiding the dereference but rather in not having to do pointer arithmetic under the hood. So in example 4-4 calling s[i] is in effect s + i. However when iterators are used this pointer arithmetic is integrated with the increment of the for loop, thereby saving that addition. However technically both example 4-4 and 4-5 still dereference pointers. |
Steve | Sep 11, 2016 | |
Page 96 last paragraph |
The line |
Jeffrey Reynolds | Dec 30, 2015 | |
Page 132 Section on Double Dispatch |
All that is displayed on the PDF is "[Double-dispatch is an optimizing strategy versus if/else and dynamic-cast. Need |
David Racey | Nov 20, 2015 | |
Printed | Page 139 first code snippet at top of page |
code says: |
Ilja van Sprundel | Sep 01, 2016 |
Printed | Page 149 4th paragraph |
A test of the optimized code runs in 636 milliseconds ... |
Anonymous | Sep 16, 2018 |