/integer_size:64 not always happening

[dajum]

I have two projects that use the same include files for variable definitions. Mostly in common blocks. I'm writing out a number of variables in one executable to be read into the other. Using unformatted sequential files.

OPEN(UNIT=NSCR1,ACCESS='SEQUENTIAL',FORM='UNFORMATTED',

+ STATUS='REPLACE',FILE='FLOMOD')

WRITE(NSCR1) NUMFLM

For example. Then read with the same commands. Except a number of the variables seem to get a type of Integer(8) in one executable and only Integer(4) in the other, so the reads fail. Yet the definitions are coming from the same place. An example is:

COMMON /FLONM5 / THRPNT(1)

INTEGER THRPNT

Are there bugs associated with the /integer_size:64 compiler option? Or are there known cases where it fails to define INTEGER declarations with the default KIND of 8? Or just something I'm missing?

Thanks,

Dave

[Kevin_D_Intel]

Not aware of any associated bugs. By design, it does not override any explicit KIND specifications.

[mecej4]

Please post a small, complete, example that can be run to reproduce the problem that you have described.

It is not clear what you mean by "definitions are coming from the same place".