Thread with 7 posts
jump to expanded post
there's a guy seemingly creating an issue on every rust repo on github telling them to turn on lto. not sure how i feel about this…
i am being careful with my words here, i'm genuinely not sure if it's bad or good.
it happens to be a weird issue to raise on touchHLE because the project is probably more likely than most to not benefit. almost the entire thing is a single crate
we could potentially significantly benefit from LTO with the C++ dependencies though… i assume this cargo flag won't do that but it'd be worth looking into how we could achieve that. maybe still a useful reminder for us then
@hikari it passes the flag to rustc, which will apply LTO when linking, so as long as you’re not linking with something else you should still see benefits from LTO aiui
you have to link the C++ dependencies in, so LTO should still work
@hikari or more accurately, turning on LTO in your package will ultimately pass that through to LLVM, which will apply it to all the intermediate objects it’s linking together to the final executable
@hikari gross
@hikari (says the girl who has CFLAGS="-march=native -O2 -flto" in her make.conf)
(actually I have a little more but I am not at my desktop to put it all in this post)