variable with name int conflicts with omp_lib

[AndyMay]

Whilst in new code I would personally avoid using variable names which are used for intrinsics, we have some old code where int is used and apparently this is conflicting with `omp_lib`. Here is a short example:

subroutine test
!$ use omp_lib
integer int
end

which gives:

host> ifx -c -fopenmp test.f90   
test.f90(3): error #6401: The attributes of this name conflict with those made accessible by a USE statement.   [INT]
integer int
--------^
compilation aborted for test.f90 (code 1)
host> ifx -v
ifx version 2023.2.0

Of course the problem is simple enough to avoid by renaming the variable.

[Ron_Green]

well that is interesting.  Seems like a regression in the oneAPI OMP Runtime since the start of the oneapi distributions.  

We'll get a bug report opened on this.  Thank you for brining it to our attention.