I’m testing an eval version of pgf90/f95 v6.0-4 and during compilation I get bzillions of messages like so:
PGF90-I-0063-Gap in common block spccoeff_define$10 before sensor_type_name$ac (radiance.f90)
PGF90-I-0063-Gap in common block spccoeff_define$10 before polarization_type_name$ac (radiance.f90)
PGF90-I-0063-Gap in common block type_kinds$9 before fp_byte_sizes$ac (radiance.f90)
etc etc etc…
I get 1000’s of these info messages with 6.0-4, but I never got them with v5 (.0,.1, or.2). I don’t use common blocks in my f95 code so I assume these are due to an internal representation of data? Is the latest pgf95 storing data inefficiently? Is there something I can do in my code to make these info messages go away? (turning them off with a compilation switch is cheating :o)
Thanks for any info.