Live data from Hacker News

From Rust to reality: The hidden journey of fetch_max

questdb.com

61–62 of 62 posts

Re: From Rust to reality: The hidden journey of fetch_max

#61

Was this compiled at O0? The generated code looks unnecessarily long-winded - at the very least I would expect the match jump table to get culled to only the Relaxed implementation.

> Note we did not ask rustc to optimize the code. If we did, the compiler would generate more efficient assembly: No spills to the stack, fewer jumps, no dispatch on memory ordering, etc. But I wanted to keep the output as close to the original IR as possible to make it easier to follow. RTFA

I did, however that call out did, admittedly, slip past me

Re: From Rust to reality: The hidden journey of fetch_max

#62

Earlier quoted context omitted.

> Note we did not ask rustc to optimize the code. If we did, the compiler would generate more efficient assembly: No spills to the stack, fewer jumps, no dispatch on memory ordering, etc. But I wanted to keep the output as close to the original IR as possible to make it easier to follow. RTFA

I did, however that call out did, admittedly, slip past me

No worries, I felt like an ass using the idiom but it was so literally appropriate.
Post reply on HN