TriCore calling convention cannot specify integer argument registers

Because the calling convention model does not identify groupings of registers (aside from integer/float) we cannot properly model TriCore's dual integer register files (a, d). This resulted in us deciding to fallback entirely to heuristics to pickup the arguments. The one main issue with that is the heuristics are not aware of the register ordering, i.e. that register 1 must be preceded by register 0.

We should either:

1. Improve our calling convention model to have a notion of register files (or groups)
2. Create a workflow that fixes up the misidentified functions, this would incur a reanalysis cost as we would likely have to re-analyze the function assuming that we cannot interject our workflow activity before any usage of the bad params.