>> This patch implementing TARGET_COMP_TYPE_ATTRIBUTES to compare "RVV type" and
>> "RVV sizeless type" and prevent the C++ frontend from treating them as
>> identical, fixing the "ambiguating new declaration" error.
>>
>> Suggested by: Zhongyao Chen <[email protected]>
>
> I'm not sure this is the right fix but rather it might just papering 
> over the actual problem.  I think we're dealing with a similar problem 
> than the XTHeadVector LTO issue from several months ago.  During type 
> registration we need to enable all modes and all extensions in order to 
> keep their order and index consistent for streaming.
>
> The issue here smells very similar but I need to do some more digging to 
> really confirm.

I did some more digging and think I have a fix for this.  But I won't 
manage to send it before Cauldron.

-- 
Regards
 Robin

Reply via email to