mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Thomas Petazzoni <>
To: "" <>
Subject: [musl] ./src/internal/atomic.h:229:14: error: size of array 'a_cas_p_undefined_but_pointer_not_32bit' is negative on PowerPC
Date: Fri, 22 Jul 2022 09:12:24 +0200	[thread overview]
Message-ID: <20220722091224.344b2b22@windsurf> (raw)


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

             reply	other threads:[~2022-07-22  7:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22  7:12 Thomas Petazzoni [this message]
2022-07-22 16:29 ` Szabolcs Nagy
2022-07-29 15:34   ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220722091224.344b2b22@windsurf \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).