News for hackers. Stuff that matters.

A comment on Saving a Third of Our Memory by Re-Ordering Go Struct Fields (2020). Parent comment

Re:Saving a Third of Our Memory by Re-Ordering Go Struct Fie... by fulafel on Monday January 10, 2022 @02:48AM (#29871719)
Yes, JIT runtimes have an easier time here (and can more easily do feedback based optimizations on access patterns). For AOT you can do LTO / whole program opt and punt on calls to outside libs, plus provide generics style specializable library code that is not AOT compiled.

I submit it's mostly solvable in language design. They're not all lazy of course, but claiming to be very performance-oriented is a half truth as long as you don't have a strong story here.

[ Parent | on HN ]
Re:Saving a Third of Our Memory by Re-Ordering Go Struct Fie... by pjmlp on Monday January 10, 2022 @03:46AM (#29872030)
That doesn't work in environments based on shared libraries or OS IPC component models.
[ Parent | on HN ]