> On 31 May 2023, at 18:57, Jeff Law via Gcc-patches <gcc-patches@gcc.gnu.org>
> wrote:
>
>
>
> On 5/31/23 10:25, Vineet Gupta wrote:
>> Multilib testing on trunk is currently busted (and surprisingly this
>> affects any/all targets but it seems nobody cares). We currently get the
>> following splat:
> I wouldn't say that nobody cares, it just hasn't bubbled up on anyone's
> priority list yet (most developers aren't working on targets that make heavy
> use of multilibs).
>
> But probably more importantly, this problem seems to not be triggering on all
> multilib targets. For example, I just examined my tester's build logs and
> couldn't see this on the H8/300 or V850 ports. Which begs the question, why?
I do have a multilib problem [with libgomp] on Darwin (which has been noticed :
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109951) but it is not obvious how
the fix proposed would solve this - unless it’s some subtle change in global
content for the multilib options.
(testing anyway)
thanks
Iain
