OpenACC device_type clause and routine bind clause are rejected ("Failed to match clause")

! # Finding (GCC 16.2): OpenACC device_type and routine bind clauses are rejected (Fortran); the reproducer is the catalog program
!   acc34-clause-device_type
!
! - toolchains: gcc_g90 (GCC 16.2.0, AMD Instinct MI250X gfx90a, Tioga) and gcc_sm80 (GCC 16.2.0,
!   NVIDIA A100 sm_80, wingtip); separate memory only; -O2; OMP_TARGET_OFFLOAD=mandatory
! - build: gfortran -fopenacc -foffload=amdgcn-amdhsa -foffload-options=amdgcn-amdhsa=-march=gfx90a -O2 (gcc_g90);
!   -foffload=nvptx-none -foffload-options=nvptx-none=-march=sm_80 -foffload-options=nvptx-none=-latomic -O2 (gcc_sm80)
! - failure: rejected
! - observed: `Error: Failed to match clause at (1)` at device_type(*) (and at the bind clause of acc34-clause-bind), on both GPUs.
!   acc34-clause-bind also reports `Invalid NAME 'host_val' in !$ACC ROUTINE (NAME )` at `!$acc routine(host_val) seq
!   bind(dev_val)`: the named form of the routine directive names a procedure gfortran does not accept there (an external
!   procedure); it is the same program's second rejection, not studied separately.
! - expected: compiles; `RESULT ran_on_host=0 check=pass`
! - spec: the device_type clause (OpenACC 3.4 §2.4 l.1013-1015) and the routine directive's bind clause (§2.15.1 l.3405-3407: "The
!   bind clause specifies the name to use when calling the procedure on a device other than the host"); both are OpenACC 2.0
!   clauses.
! - GCC 16.2 documentation (libgomp.texi "Enabling OpenACC"): "A complete description of all OpenACC directives accepted may be
!   found in the OpenACC Application Programming Interface manual, version 2.6"; _OPENACC is 201711 (2.6). No list of OpenACC gaps
!   is documented.
! - other families: CCE 19/20/21 (MI300A, MI250X) and NVHPC 25.11/26.9 compile and run both programs correctly.
! - gate and confirmer: 4 cells (2 gcc_g90, 2 gcc_sm80), each confirmed in the gate's four environments (a-d;
!   results/gcc/gate-tioga/ and gate-wingtip/ verdicts.jsonl); confirmer verdicts (results/gcc/confirm/batch.gcc_*.jsonl):
!   compiler_bug (R11-compile-rejection) 4
! - catalog programs (2): acc34-clause-bind, acc34-clause-device_type
! - legality: the catalog programs are legal by construction (offload.engine.gen, c_gen and acc_gen
!   check every program against the catalog rules and the offload scope as it is built; no
!   compiler). GCC is a compiler under test only: never a legality witness, here or for another
!   family's case (catalog/machines.yaml under_test_only).
! Generated by compliance.gen (OpenACC 3.4, free-form Fortran). Do not edit.
! id: acc34-clause-device_type
! primary atom: acc.clause.device_type
! legal: yes
! observable: yes
! ran_on_host: inside the compute region of interest (acc_on_device)
! evidence: implementation_defined
! needs: none
! std: f2008
! no oracle (implementation_defined): the device types and their names are implementation-defined; the clauses after device_type(*)
! are hints here (vector_length)
! basis: OpenACC 3.4 §2.4, p.32: "The supported device types are implementation-defined."
program gen_prog
  use openacc, only: acc_device_host, acc_on_device
  implicit none
  integer, parameter :: n = 64
  integer, allocatable, target :: a(:), b(:)
  integer :: ref(n)
  integer :: i, host_flag
  logical :: ok
  allocate(a(n), b(n))
  do i = 1, n
    a(i) = i
    b(i) = 0
    ref(i) = 2*i + 1
  end do
  host_flag = 1
  !$acc parallel loop copyin(a) copyout(b) copy(host_flag) device_type(*) vector_length(32)
  do i = 1, n
    if (i == 1) host_flag = merge(1, 0, acc_on_device(acc_device_host))
    b(i) = 2*a(i) + 1
  end do
  ok = all(b == ref)
  print '(a,i0,a,a)', 'RESULT ran_on_host=', host_flag, ' check=', merge('pass', 'fail', ok)
  deallocate(a, b)
end program gen_prog