[PATCH v3] Fix POSIX compliance: Make blkcnt_t and blksize_t signed on alpha

[Collin Funk]

Adhemerval Zanella Netto <adhemerval.zanella@linaro.org> writes:

> For the context provided in the bug report [1], the issues is from a
> _Static_assert tat is already being handled in the m4 project. I am
> more inclined in not act on this issue unless this is a read issue
> where the non-POSIX compliance is causing some semantic or usability
> issue.
>
> [1] https://lists.gnu.org/archive/html/bug-m4/2025-09/msg00000.html

The test is imported into the m4 tarball, it is really from Gnulib. The
downstream m4 maintainer just happened to notice it there.

We check it because we define the type on some platforms where it is not
defined. And we want those definitions to conform with POSIX and not
be some random type.

I thought it was likely too late to change it when creating the bug
report. But I figured it was worth a bug report since it is the only
platform with the wrong signedness.

Anyways, thanks all for checking.

Collin