Timeline for answer to When did compilers start generating optimized code that runs faster than an average programmer's assembly code? by Chromatix
Current License: CC BY-SA 4.0
Post Revisions
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 22, 2021 at 9:58 | comment | added | MSalters | @MarkRansom: Modern compilers do understand range restrictions. See e.g. stackoverflow.com/questions/40447195/… | |
| Sep 29, 2021 at 16:14 | comment | added | Mark Ransom |
Sometimes the assembly programmer can take advantage of knowledge of the problem that the compiler can't know. For example (n * 103) >> 10 is equivalent to n / 10, if you know that n is an integer in the range 0 to 99. Compilers know lots of tricks like that, but they don't know that your input is restricted.
|
|
| S Sep 14, 2020 at 20:51 | history | suggested | Reid | CC BY-SA 4.0 |
change to gender neutral
|
| Sep 14, 2020 at 19:48 | review | Suggested edits | |||
| S Sep 14, 2020 at 20:51 | |||||
| S Sep 14, 2020 at 15:27 | history | mod moved comments to chat | |||
| S Sep 14, 2020 at 15:27 | comment | added | Chenmunka♦ | Comments are not for extended discussion; this conversation has been moved to chat. | |
| Sep 12, 2020 at 9:43 | history | answered | Chromatix | CC BY-SA 4.0 |