[PATCH 46/59] ctf, link: fix spurious conflicts of variables in the variable section

[Nick Alcock]

On 1 Jul 2020, Nick Alcock via Binutils outgrape:

> When we link a CTF variable, we check to see if it already exists in the
> parent dict first: if it does, and it has a type the same as the type we
> would populate it with, we assume we don't need to do anything:
> otherwise, we populate it in a per-CU child.

Well, OK, this commit log is getting changed. It stuck out a mile in the
mailing list summary view :)

'ctf'? No, libctf!