Build fails with gcc 14.1.1

[BanditSan]

Long story short

While installing python-caio from AUR build fails with latest gcc 14.1.1 Arch linux package.

python -m build --wheel --no-isolation fails with error:

caio/linux_aio.c: In function ‘AIOOperation_read’:
caio/linux_aio.c:577:25: error: assignment to ‘__u64’ {aka ‘long long unsigned int’} from ‘AIOOperation *’ makes integer from pointer without a cast [-Wint-conversion]
  577 |     self->iocb.aio_data = self;
      |                         ^
caio/linux_aio.c: In function ‘AIOOperation_write’:
caio/linux_aio.c:630:25: error: assignment to ‘__u64’ {aka ‘long long unsigned int’} from ‘AIOOperation *’ makes integer from pointer without a cast [-Wint-conversion]
  630 |     self->iocb.aio_data = self;
      |                         ^
caio/linux_aio.c: In function ‘AIOOperation_fsync’:
caio/linux_aio.c:706:25: error: assignment to ‘__u64’ {aka ‘long long unsigned int’} from ‘AIOOperation *’ makes integer from pointer without a cast [-Wint-conversion]
  706 |     self->iocb.aio_data = self;
      |                         ^
caio/linux_aio.c: In function ‘AIOOperation_fdsync’:
caio/linux_aio.c:751:25: error: assignment to ‘__u64’ {aka ‘long long unsigned int’} from ‘AIOOperation *’ makes integer from pointer without a cast [-Wint-conversion]
  751 |     self->iocb.aio_data = self;
      |                         ^
error: command '/usr/bin/gcc' failed with exit code 1

Build succeeds with gcc and gcc-libs downgraded to 13.2.1 latest gcc 13 available on Arch linux.

Expected behavior

Successful build.

Actual behavior

Build fails.

Steps to reproduce

python -m build --wheel --no-isolation with gcc 14.1.1

Environment info

Kernel version: 6.9.1-zen1-2-zen #1 ZEN SMP PREEMPT_DYNAMIC Wed, 22 May 2024 13:47:12 +0000 x86_64 GNU/Linux
File system: btrfs

I have been produced this problem with implementations:

• [] export CAIO_IMPL=linux - Native linux implementation
• [] export CAIO_IMPL=thread - Thread implementation
• [] export CAIO_IMPL=python - Pure Python implementation

Additional info

I suspect this is not Arch linux specific issue but caused by some major changes between gcc 13 and gcc 14