> I am not quite sure I understand your explanation. Can you, please, show me
> how the types differ? So you have one type which contains ptr_type_node and
> other which is array?
For one compilation unit, the type is an array of pointer to something, for
example a record type and, for another c
> This change makes it so that gigi uses a generic pointer type (ptr_type_node)
> for pointers to Taft Amendment types, which are kind of opaque pointer types.
>
> Tested on x86_64-suse-linux, applied on the mainline.
>
> However, this isn't sufficient for LTO's type canonical merging code, beca
This change makes it so that gigi uses a generic pointer type (ptr_type_node)
for pointers to Taft Amendment types, which are kind of opaque pointer types.
Tested on x86_64-suse-linux, applied on the mainline.
However, this isn't sufficient for LTO's type canonical merging code, because
the gen
