Behavior of IBSET

Behavior of IBSET

Consider the following program:

program test
end program test

Here's the result:

$ ifort -o test test.f90
$ ./test
$ ifort -V
Intel(R) Fortran Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version Build 20121010
Copyright (C) 1985-2012 Intel Corporation.  All rights reserved.

Shouldn't the compiler throw an error in such cases?

7 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

 ifort -stand sk.f

        program test
sk.f(2): warning #7376: Standard F2003 requires POS, the 2nd argument, be less than BIT_SIZE of I, the 1st argument.   [IBSET]

Is your point that the code should be rejected regardless of option setting?

gfortran  sk.f

Error: 'pos' at (1) must be less than BIT_SIZE('i')

Yeah, I would expect it to do so, like gfortran does. I was not aware that the requirement POS < BIT_SIZE was introduced only in F2003 though.

The -stand option defaults to checking against f2003.  I expect the similar warning if you set checking against other standards.

You are likely to find many cases where the default in Intel Fortran is to let you express things not supported by the standard. Usually this is for historical compatibility. In such cases asking for standards checking gets you additional diagnostics.

Retired 12/31/2016

Thanks for the clarification, I'll start using -stand to this end from now on. One more marginally related question: can the -stand option interfere in any way with optimization?

It's not supposed to - it enables additional diagnostics only and does not change compiler semantics. There have been compiler bugs in the past where it did, but I am not aware of any cases nowadays.

Retired 12/31/2016

Leave a Comment

Please sign in to add a comment. Not a member? Join today