TI Arm Clang mismatch between source code and debugger view with function subsections

When code is compiled with debug and function subsections, functions that are not actually called in the program may show up in the debugger with ranges that overlap with other functions. This is because the TI Arm Clang compiler emits all debug info for an object file in the same section even when function subsections are used. The executable code for functions that are not called won't be included in the program when function subsections are used, but if there were any other functions in the same source file that were called, their debug info will still get pulled in. Because the uncalled functions don't have actual addresses, their debug info will have low addresses of 0, leading to overlap in the debug view with any other functions in that range.