Added StructTest.c Struct Layout Output for Two Computers

Author: Thomas Weise

mpi/README.md

@@ -125,6 +125,8 @@ Build: `mpicc reducePrimes.c -o reducePrimes -lm`
 This example does no communication at all, but it prints the memory layout of a `struct`. This shows that the compiler may align fields in many ways and we cannot compute on where a field of a `struct` but need to use proper addressing. 
 
 1. [structTest.c](http://github.com/thomasWeise/distributedComputingExamples/tree/master/mpi/structTest.c)
+2. [structTest_32bit_intel_atom_N280_gcc_4.8.4.txt](http://github.com/thomasWeise/distributedComputingExamples/tree/master/mpi/structTest_32bit_intel_atom_N280_gcc_4.8.4.txt)
+2. [structTest_64bit_intel_xeon_e3-1230_gcc_5.2.1.txt](http://github.com/thomasWeise/distributedComputingExamples/tree/master/mpi/structTest_64bit_intel_xeon_e3-1230_gcc_5.2.1.txt)
 
 Build: `mpicc structTest.c -o structTest`
 

mpi/structTest_32bit_intel_atom_N280_gcc_4.8.4.txt

@@ -0,0 +1,8 @@
+Struct is 28 bytes large.
+Field "myIntA"   begins at offset 0 and is 4 bytes large.
+Field "myIntB"   begins at offset 4 and is 4 bytes large.
+Field "myShort"  begins at offset 8 and is 2 bytes large.
+Field "myDouble" begins at offset 12 and is 8 bytes large.
+Field "myChar"   begins at offset 20 and is 1 bytes large.
+Field "myFloat"  begins at offset 24 and is 4 bytes large.
+Effectively used data size is 23.

mpi/structTest_64bit_intel_xeon_e3-1230_gcc_5.2.1.txt

@@ -0,0 +1,8 @@
+Struct is 32 bytes large.
+Field "myIntA"   begins at offset 0 and is 4 bytes large.
+Field "myIntB"   begins at offset 4 and is 4 bytes large.
+Field "myShort"  begins at offset 8 and is 2 bytes large.
+Field "myDouble" begins at offset 16 and is 8 bytes large.
+Field "myChar"   begins at offset 24 and is 1 bytes large.
+Field "myFloat"  begins at offset 28 and is 4 bytes large.
+Effectively used data size is 23.