Hacker News Reader

> Handling banks is normally a tedious affair for programmers, but NESFab handles it for you. The compiler smartly allocates code and data into banks, with the gritty details abstracted away.

Killer feature, but is there a cost to bank switching? Could abstracting it result in a lot of performance cost?

View on HN

There is a cost: subroutine calls get wrapped in something called a trampoline, and some data is duplicated across multiple banks. You would do both of these things in assembly language too, and could even do it more optimally, but it's an NP-hard problem and takes a lot of thinking.

Most practical instances of most NP-hard problems are quite tractable with something like an Integer Programming solver or an SMT solver.

Reply on news.ycombinator.com