Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
3 Views

#6375: Because of COMMON, the alignment of object is inconsistent with its type

Hi,

I saw this topic for the visual Fortran compiler for Windows, I get the same warning on OSX for a code that I didn't write.

#6375: Because of COMMON, the alignment of object is inconsistent with its type

https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/296523

What does it mean? what are the "potential performance impact"?

Thanks

GB

0 Kudos
6 Replies
Highlighted
Black Belt
3 Views

For example, you might have

For example, you might have an odd number of 32 bit data followed by 64 bit data.  That could result in a data access requiring references to 2 cache lines and the hardware piecing the 2 together or splitting them, which may be slow even though you probably have a hardware platform which supports it. 

0 Kudos
Highlighted
Beginner
3 Views

Thanks Tim,

Thanks Tim,

So the only risk is that my code slows down, am I right? My results shouldn't be affected.

 

 

0 Kudos
Highlighted
Black Belt
3 Views

Yes, it's ok, as long as you

Yes, it's ok, as long as you don't set a nonstandard padding option and use it inconsistently.
0 Kudos
Highlighted
Beginner
3 Views

Isn't there a preferred

Isn't there a preferred practice, when using COMMON, to list variables largest first, e.g., 64-bit, then in decreasing order of size?  Of course, you need to change all references to the common block.

j

 

 

0 Kudos
Highlighted
Beginner
3 Views

I didn't know about it.

I didn't know about it.

0 Kudos
Highlighted
Beginner
3 Views

Jayb is your question an

Jayb is your question an answer?or are you wondering about it like me?

0 Kudos