Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

On #9, is it 16-bit or 64-bit values? Sounds like you may have been answering a different question. Isn't the standard answer to use a 65536 entry lookup table?

Edit: oh, are you reinterpreting the array of 10000 16-bit integers as 2500 64-bit integers? But then what operation do you use on each?

Either way, if you find yourself arguing with the recruiter, it's probably a bad sign.



I thought the reason it was generally accepted that the 8-bit lookup table is optimal is because it can fit in the L1 cache.


(Very) embedded developer speaking here. What's this L1 cache you speak of?


It's level 1 CPU cache, the fastest (and smallest) cache.

It caches both instructions and data.

https://en.wikipedia.org/wiki/CPU_cache


It was a joke. Some embedded processors lack a cache.


GP is making the point that not all CPUs have a cache.


> Isn't the standard answer to use a 65536 entry lookup table?

Yes, it is, but is it such a common knowledge?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: