Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Fri, 22 Jul 2022 09:12:24 +0200
From: Thomas Petazzoni <>
To: "" <>
Subject: ./src/internal/atomic.h:229:14: error: size of array
 'a_cas_p_undefined_but_pointer_not_32bit' is negative on PowerPC


We've "recently" started in Buildroot the build testing of fully random
configurations, so we're now testing many more cases and seeing new
build failures.

As part of this, we're now seeing build failures of musl on PowerPC
32-bit architectures. So far, we've seen the problem on power4
(-mcpu=power4), power5 (-mcpu=power5) and power6 (-mcpu=power6), 970
(-mcpu=970), power8 (-mcpu=power8), 620 (-mcpu=620), 630 (-mcpu=630).

The failure is:

./src/internal/atomic.h:229:14: error: size of array 'a_cas_p_undefined_but_pointer_not_32bit' is negative
  229 | typedef char a_cas_p_undefined_but_pointer_not_32bit[-sizeof(char) == 0xffffffff ? 1 : -1];
      |              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

You can see the full musl build log at: (power4) (power5) (power6) (970) (power8) (620) (630)

I have not investigated the problem so far. I'm not super familiar with
PowerPC, but it seems like these cores are all 64-bit capable, but here
we build for them in 32-bit mode. Maybe this is the case that isn't
handled or supported by musl?

Thanks a lot for your support!

Best regards,

Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.