objdiff pairs up unrelated compiler-generated symbols that happen to have the exact same name #216
Description
MWCC names most compiler-generated objects like @1234 with no distinction as to what they are, so sometimes the name of an object on the left will happen to be exactly the same as a totally different object on the right.
For example, here's a switch statement jump table in the left side's .data section that should be considered 100% matching, but is instead considered 1% matching:
It's because there's a float literal that happens to have the exact same name on the right (in the .sdata2 section), so objdiff considers them the same:
Not sure what the best solution would be here, maybe for compiler-generated objects disable pairing them up by name and only look at address and data contents?