Timeline for Storage usage of methods compared to copied code
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 27, 2017 at 22:05 | comment | added | Majenko |
__attribute__((always_inline)).
|
|
| Nov 27, 2017 at 21:29 | comment | added | frarugi87 | The optimization is in the last remark; I could have highlighted it more. Moreover how can you force the compiler to inline? I thought that the "inline" keyword was just a hint; is there another keyword to force the inlining? | |
| Nov 27, 2017 at 15:18 | comment | added | Majenko | You haven't mentioned optimization: if you use a function only once the compiler will most likely just place the code inline, thus avoiding the overhead of a function. You can also force a function to be inline, so you have the convenience of no duplicate code coupled with the efficience of inline code. | |
| Nov 27, 2017 at 14:51 | vote | accept | Lehue | ||
| Nov 27, 2017 at 14:41 | history | answered | frarugi87 | CC BY-SA 3.0 |