Timeline for Is it bad practice to write code that relies on compiler optimizations?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 13, 2017 at 9:32 | comment | added | Marc Glisse | This optimization isn't quite as robust as one might like. Yes, it is rather reliable in the most obvious cases, but looking for instance at gcc's bugzilla, there are many barely-less-obvious cases where it is missed. | |
| Oct 12, 2017 at 21:04 | comment | added | user22815 | The key here is it is not some random compiler-specific optimization or "undocumented feature," but something that, while technically optional in several versions of the C++ standard, was heavily pushed by the industry and pretty much every major compiler has done it for a very long time. | |
| Oct 12, 2017 at 16:13 | comment | added | nwp | Just for fun see how Borland Turbo C++ 3.0 from 1990-ish handles RVO. Spoiler: It basically works just fine. | |
| Oct 12, 2017 at 15:31 | history | answered | Quentin | CC BY-SA 3.0 |