topic Re: FORTRAN Compile Link Error in Operating System - OpenVMS

FORTRAN Compile Link Error

MJ26 — Wed, 17 Nov 2010 16:04:22 GMT

I am receiving the following error when I compile the following code:

prvmsk(1) = ( prv$m_bypass .or. prv$m_cmkrnl .or.
......................^
%F90-W-WARNING, Overflow occurred while evaluating constant expression.
at line number 60 in file DKA0:[CODE]DEFRAG.FOR;30

If I limit the amount of .or. statements, it compiles just fine. I also noticed that if I move the prv$m_share to the front, it fails as well. So I'm not sure if there is an order of precedence as to what is being checked, or if that IA64 compiler is acting funny with the entire statement. It does compile on an Alpha with no issues.

c
c define the system parameters
c
include '($prvdef)'
c
c define the functions referenced
c
integer sys$setprv, sys$bintim
integer lib$get_symbol, lib$set_symbol
integer str$position
c
c define the external references
c

c
c define the local parameters
c

c
c define the local variables
c
character*1024 cmd_str, vol_str, qual_str
character*255 p1_str, p2_str, p3_str, func_str
character*32 end_str
integer p1_len, p2_len, p3_len, func_len
integer cmd_len, vol_len, qual_len
integer iret, i, prvmsk(2), end_len
integer*4 end_time(2)
c
c get the proper privileges
c
prvmsk(1) = ( prv$m_bypass .or. prv$m_cmkrnl .or.
1 prv$m_detach .or. prv$m_netmbx .or. prv$m_sysgbl .or.
2 prv$m_world .or. prv$m_syslck .or. prv$m_sysprv .or.
3 prv$m_tmpmbx .or. prv$m_share )
iret = sys$setprv ( %val(1), prvmsk, , )
c
c get the parameters for this operation
c
iret = lib$get_symbol ( 'P1', p1_str, p1_len )
iret = lib$get_symbol ( 'P2', p2_str, p2_len )
iret = lib$get_symbol ( 'P3', p3_str, p3_len )
c
c special case check for HOST function
c
if ( p1_str(:p1_len) .eq. 'HOST' ) then
call update_host_list ( p2_str(:p2_len) )
goto 800
endif
c
c extract the function from the qualifiers
c
i = str$position ( p1_str(:p1_len), '/' )
if ( i .gt. 0 ) then
call str$trim ( func_str, p1_str(:i-1), func_len )
call str$trim ( qual_str, p1_str(i:p1_len), qual_len )
else
call str$trim ( func_str, p1_str(:p1_len), func_len )
call str$trim ( qual_str, ' ', qual_len )
endif
c
c extract the end time from the P3
c
call str$element ( end_str, 1, ',', p3_str(:p3_len) )
call str$trim ( end_str, end_str, end_len )
i = str$position ( end_str(:end_len), ':' )
end_str(i:i) = ' '
iret = sys$bintim ( end_str(:end_len), end_time )
if (.not. iret) call sys$gettim ( end_time )
c
c generate the command needed for this function
c ABORT is easy, need a subroutine for the FILE and FREE passes
c
if ( func_str(:func_len) .eq. 'ABORT' ) then
call sys$fao ( 'DEFRAGMENT ABORT !AS', cmd_len, cmd_str,
1 p2_str(:p2_len) )
call str$trim ( vol_str, ' ', vol_len )
call lib$set_symbol ( 'DEFRAG_VOL', vol_str(:vol_len) )
call lib$set_symbol ( 'DEFRAG_FIX', vol_str(:vol_len) )
else
call sys$fao ( 'DEFR VOLU !AS', cmd_len, cmd_str,
1 p2_str(:p2_len) )
call set_vol_symb ( func_str(:func_len), p2_str(:p2_len),
1 end_time )
if ( func_str(:func_len) .eq. 'FILE' ) then
call lib$set_symbol ( 'DEFRAG_FIX',
1 '/NOCONS/PROL=P_FILE/EPIL=P_FILE' )
else
call lib$set_symbol ( 'DEFRAG_FIX',
1 '/CONS/PROL=P_FREE/EPIL=P_FREE' )
endif
endif
c
c create the base command and required qualifier symbols
c
call lib$set_symbol ( 'DEFRAG_CMD', cmd_str(:cmd_len) )
call lib$set_symbol ( 'DEFRAG_QUAL', qual_str(:qual_len) )
c
c that's all
c
800 continue
end

Re: FORTRAN Compile Link Error

Steven Schweda — Wed, 17 Nov 2010 16:53:29 GMT

> If I limit the amount of .or. statements,
> [...]

What, exactly, does that mean? (And ".or."
is an operator, not a statement.)

> I also noticed that if I move the
> prv$m_share to the front, it fails as well.

Why would you do that?

What, exactly, seems to work, and what,
exactly, seems to fail?

I'd guess that a much shorter test case would
show the problem just as well.

If throwing out PRV$M_SHARE helps, then,
knowing nothing, I'd guess that it's a
sign-bit problem. PRV$M_SHARE = 0x80000000.)
I wouldn't expect a logical operator to
trigger an overflow complaint, however.

Re: FORTRAN Compile Link Error

abrsvc — Wed, 17 Nov 2010 16:53:43 GMT

For grins, take out the PRV_SHARE and see if that compiles OK. That one sets the "sign" bit and maybe causing a problem. The code should work. Please report the results.

Dan

Re: FORTRAN Compile Link Error

MJ26 — Wed, 17 Nov 2010 16:58:27 GMT

I removed the prv$m_share, and yes, it did compile successfully. Any thoughts as to why it would not like prv$m_share?

Re: FORTRAN Compile Link Error

Steven Schweda — Wed, 17 Nov 2010 17:06:44 GMT

> [...] Any thoughts as to why it would not
> like prv$m_share?

Are you reading these responses?

Re: FORTRAN Compile Link Error

Hein van den Heuvel — Wed, 17 Nov 2010 17:12:40 GMT

Fortran integers are signed.
The value for SHARE does NOT fit.
It is 1 higher than the max.

Much like DCL:

$ x=%x80000000
$ sho sym x
X = -2147483648 Hex = 80000000 Octal = 20000000000

So you could use "-2147483648" instead of _SHARE.

Or just simply use -1 and get ALL privs :-)

Oddly (imho) LOGICAL(KIND=4) has the same restriction.

You could just use a 64 bit mask in one go:

integer(kind=8) prvmsk
prvmsk = ( prv$m_bypass .or. ... prv$m_share )
iret = sys$setprv ( %val(1), prvmsk, , )

That works.
Or you can play with equivalences and HEX constants

Or use a language that can handle 'unsigned'

fwiw,
Hein

Re: FORTRAN Compile Link Error

MJ26 — Wed, 17 Nov 2010 17:19:16 GMT

Hein - Thanks! That worked:

integer(kind=8) prvmsk
c
c get the proper privileges
c
prvmsk = ( prv$m_bypass .or. prv$m_cmkrnl .or.
1 prv$m_detach .or. prv$m_netmbx .or. prv$m_sysgbl .or.
2 prv$m_world .or. prv$m_syslck .or. prv$m_sysprv .or.
3 prv$m_tmpmbx .or. prv$m_share )
iret = sys$setprv ( %val(1), prvmsk, , )

Appreciate the assistance and explanation.

Re: FORTRAN Compile Link Error

MJ26 — Wed, 17 Nov 2010 17:19:42 GMT

Hein's suggestion worked successfully. Closing thread.

Re: FORTRAN Compile Link Error

Hein van den Heuvel — Wed, 17 Nov 2010 17:23:19 GMT

Actually, using HEX notation would not work. That's what the include file does:

PARAMETER PRV$M_SHARE = '80000000'X

I like using the BIT definitions instead of the MASKS

I would also not be above defining a fresh, negative, constant with all the right bits set and a name + comment to indicate that.
To construct the value I would once use DCL and libr/extr=$prvdef/out=tt: sys$library:FORSYSDEF.TLB

fwiw,
easy read on the limit on integers:
http://docs.hp.com/en/B3909-90002/ch08s01.html

Hein

Re: FORTRAN Compile Link Error

Mike Kier — Wed, 17 Nov 2010 18:47:01 GMT

Or you could use the bit number symbols with the intrinsic IBSET - I don't have an Integrity system to test on, so I don't know if it would throw the warning.

I also think the code is more readable and the intent is clearer that you're explicitly setting bits in a mask:

prvmsk = 0
prvmsk = IBSET(prvmsk, PRV$V_SHARE)
prvmsk = IBSET(prvmsk, PRV$V_BYPASS)
.
.
.

Re: FORTRAN Compile Link Error

Joseph Huber_1 — Wed, 17 Nov 2010 19:18:25 GMT

The real problem is not integer overflow for default (kind=4) integers, but the in fact misusing the .OR. operator with integer constants.
I know it is handy to write it in a single concatenation of .or.s, and works in most cases.
The correct usage for integer oring is IOR(int1,int2).
The following is the correct integer ORing and does not need to have prvmsk defined as a 64 bit quantity, which has to be converted back into a 32bit quantity in the sys$... call.
VMS is little endian; on a big-endian system passing a 64bit integer to a routine expecting a 32bit integer would fail!

program test

include '($prvdef)'
integer sys$setprv

integer(kind=4) prvmsk
integer iret

prvmsk=IOR( prv$m_share,IOR(prv$m_tmpmbx,&
IOR(prv$m_sysprv,IOR(prv$m_syslck,&
IOR(prv$m_world,IOR(prv$m_netmbx,IOR(prv$m_cmkrnl,&
IOR(prv$m_detach,prv$m_bypass))))))))
print *, prvmsk

iret = sys$setprv ( %val(1), prvmsk, , )
call exit(iret)
end

Re: FORTRAN Compile Link Error

Hein van den Heuvel — Wed, 17 Nov 2010 19:41:08 GMT

>> The correct usage for integer oring is IOR(int1,int2).

Thanks for the reminder.
The (Alpha) compiler likes that.

>> does not need to have prvmsk defined as a 64 bit quantity, which has to be converted back into a 32bit quantity in the sys$... call.

The prvmsk is actually a 64 bit structure.

Hein

Re: FORTRAN Compile Link Error

Joseph Huber_1 — Wed, 17 Nov 2010 21:00:10 GMT

>The prvmsk is actually a 64 bit structure.

Ah sorry, I overlooked that!

And the way $PRVDEF defines the PRV$M_* values
for bits above bit 31 ('00000000'X) will not work for .OR. or IOR(), at least in my 7.3-1 system, only the IBSET() method works correct:
e.g.
integer(kind=8) prvmsk
prvmsk=IOR(prv$m_security,prvmsk) does not change prvmsk.
The attached program prints the result.

Is this corrected in newer versions ?

Re: FORTRAN Compile Link Error

Joseph Huber_1 — Wed, 17 Nov 2010 21:14:20 GMT

The result on my system OpenVMS V7.3-1
is

run test_priv
F0110021
70110021
F0110021
F0118021
40F0118021
40F0118021

i.e. the 40xxxxxxxx for SECURITY is not set with .OR.prv$M_security or IOR(prv$M_security,prvmsk), only with IBSET.

Re: FORTRAN Compile Link Error

Joseph Huber_1 — Wed, 17 Nov 2010 21:28:04 GMT

And it is even (half:-) documented in the 7.3 system services manual:

Each bit has a symbolic name. The $PRVDEF macro defines these names. You form the bit vector by specifying the symbolic name of each desired privilege in a logical OR operation. The following table provides the symbolic name and description of each privilege:

And the table then lists the high order bits as PRV$V_mumble.
But of course one can not OR those.

So MJ26, take care in Your program not to use those privileges or switch from OR to IBSET !