4 ms·
> LTO is aggressive by nature, and there’s no guarantee that all parts of the project will react nicely to it. In this case, the problem was Qt, the UI looked c
by saagarjha 4y ago
> LTO is aggressive by nature, and there’s no guarantee that all parts of the project will react nicely to it. In this case, the problem was Qt, the UI looked completely garbled.
Curious how LTO broke this…
- rowanG077 4y agoThis is pretty damning to me. An optimization that unsound is crazy scary.
- psychphysic 4y agoVery interesting isn't it. So LTO would remove code it considers unreachable (but really whole functions)? And that did it rather than reshuffling code for cache purposes (which is what LTO does in my mind). Cant LTO just be turned off for the QT objects in the interim?