Timeline for What determines the "speed" of a programming language?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 26, 2018 at 19:25 | comment | added | Archimedes Trajano | That's usually if you do -O0 it won't do any optimizations. Optimizations are a bonus you get with the compiler, but the language in itself can translate near one to one to assembly. | |
| Mar 15, 2015 at 19:19 | comment | added | supercat | Historically, C was designed to allow easy translation into machine code. To an increasing extent, however, turning C into efficient C code requires that a compiler figure out what a programmer was trying to do and then translate that intention into machine code. For example, historically the machine code equivalent of *p++=*q++; would on many machines have been faster than array1[i]=array2[i]; but on many processors the reverse is often true and thus compilers may end up converting the former style of code to the latter--hardly a "shallow" conversion. | |
| Mar 14, 2015 at 18:15 | review | First posts | |||
| Mar 14, 2015 at 18:37 | |||||
| Mar 14, 2015 at 18:11 | history | answered | Archimedes Trajano | CC BY-SA 3.0 |