In analyze_calls, we need to analyze a function's calls, and be able to track where they go. Given that a jal call only has a function name, it's possible for it to go to a function in any overlay. Therefore, we need to disambiguate across overlays.
We do this by identifying what overlay every function is in. This comes from the filename of the assembly file.
Since the overlay might be in, for example, asm/us/dra (a "level 3 overlay" because it has 3 directory names) or asm/us/st/cen (a "level 4 overlay") we had special logic for testing for "st".
Now that we can also have level 4 overlays in "boss" (with Maria and BO3 coming up) we need to test for those too.
While we're at it, we also only run on the "us" version's assembly files.
In analyze_calls, we need to analyze a function's calls, and be able to track where they go. Given that a
jalcall only has a function name, it's possible for it to go to a function in any overlay. Therefore, we need to disambiguate across overlays.We do this by identifying what overlay every function is in. This comes from the filename of the assembly file.
Since the overlay might be in, for example, asm/us/dra (a "level 3 overlay" because it has 3 directory names) or asm/us/st/cen (a "level 4 overlay") we had special logic for testing for "st".
Now that we can also have level 4 overlays in "boss" (with Maria and BO3 coming up) we need to test for those too.
While we're at it, we also only run on the "us" version's assembly files.