As Thomas reported in https://gcc.gnu.org/pipermail/gcc-patches/2022-January/588448.html a test added in my recent allocate clause patch fails on m32. It was due to default kind for integer matching c_intptr_t for m32. I have now changed it to 0_1 so that always integer with kind=1 is used.
gcc/testsuite/ChangeLog: * gfortran.dg/gomp/allocate-2.f90: Change 0 to 0_1. --- gcc/testsuite/gfortran.dg/gomp/allocate-2.f90 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/testsuite/gfortran.dg/gomp/allocate-2.f90 b/gcc/testsuite/gfortran.dg/gomp/allocate-2.f90 index 88b2d26872d..657ff44d023 100644 --- a/gcc/testsuite/gfortran.dg/gomp/allocate-2.f90 +++ b/gcc/testsuite/gfortran.dg/gomp/allocate-2.f90 @@ -33,7 +33,7 @@ subroutine foo(x) x=5 !$omp end parallel - !$omp parallel allocate (0: x) private(x) ! { dg-error "Expected integer expression of the 'omp_allocator_handle_kind' kind at .1." } + !$omp parallel allocate (0_1: x) private(x) ! { dg-error "Expected integer expression of the 'omp_allocator_handle_kind' kind at .1." } x=6 !$omp end parallel -- 2.25.1