#320 Inappropriate macro expansion in linker list file

[Robert Pearce]

In a current P16F1705 project I have a source file in which I define a 3-argument macro then invoke it four times.
The list file from gpasm, for just that file, correctly expands the macro on each invocation with (partial, due to relocations) hex listing.
The list file from gplink, however, does not expand the invocations at all. Instead, it expands the definition, with addresses from one of (but not the first) use, and register references from a mix of all four.
List file attached - look around line 2210 and note the registers addressed by the expansion of the ctr argument