Skip to content

Comment on Correctly implementing a spinlock in Modern C++parent

Comments

Because we live in a society and not every program can live it's life without affecting others

I write embedded code that lives in the woods like a hermit.

Favor local variables over global variables where able.

RAM is a global variable

I never leave L1.

I did once write a small program for the PDP-10 that ran entirely in the registers (which happened also to be addressable as the first 18 words of memory)

What did it do?

Something dull like compute fibbonaci numbers. Though there was a legit reason to do this: IIRC this procedure was how you bootstrapped the machine.

I never leave the trace cache. FEEB.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.