In all protocols:
----------------- 
 Size of one Fortran REAL             =            4
 Size of one Fortran DOUBLE PRECISION =            8

Results:
--------
 
 a / b / c = Alignments of:
 - DOUBLE PRECISION within a SEQUENCE derived type = a
 - DOUBLE PRECISION within a BIND(C)  derived type = b
 - MPI_DOUBLE_PRECISION (= k_i in MPI-2.2 p.78:45) = c
  
A) The 4 / 8 / 4 group = alignment of MPI_DOUBLE_PRECISION is correct for (old-style) SEQUENCE derived types 
 
JeffSquyres_OpenMP_linux-x86-64-ifort.txt:    Intel     + OpenMPI  on x86-64      Results: 4 / 8 / 4
FabTillier_Intel+MicrosoftMPI_out.txt:        Intel     + MS-MPI   on ?           Results: 4 / 8 / 4
  
B) The 4 / 8 / 8 group = alignment of MPI_DOUBLE_PRECISION is correct for (modern) BIND(C) derived types 

Rajeev_mpich_out.ifort.x86-64.txt:            Intel     + mpich2   on x86-64      Results: 4 / 8 / 8
Rolf_asama+cray_output.txt:                   Intel     + NEC-MPI? on asama       Results: 4 / 8 / 8
BillLong_Cray_5compiler_out.txt:              Intel     + CrayMPI  on Cray XE6    Results: 4 / 8 / 8
BrianSmith-IBM_outlog-bgp-xl.txt:             Intel     + IBM-XL   on BGP         Results: 4 / 8 / 8
BrianSmith-IBM_outlog-xlf.txt:                xlf       + IBM-XL   on BGQ         Results: 4 / 8 / 8
mpi_align_Supalov_MPI3-Fortran.xlsx           Intel     + IMPI     on IA64        Results: 4 / 8 / 8

C) The 4 / 4 / 8 group = Fortran alignment is always 4, but the MPI tells 8 byte

CharlesArcher-IBM_xlf+IBMmpi_onAIX.txt        xlf       + IBM PE MPI  on AIX      Results: 4 / 4 / 8

D) No problems because all DOUBLE PRECISION alignments are identical = 8
 
BillLong_Cray_5compiler_out.txt:              PGI       + CrayMPI  on Cray XE6    Results: 8 / 8 / 8
BillLong_Cray_5compiler_out.txt:              Cray      + CrayMPI  on Cray XE6    Results: 8 / 8 / 8
BillLong_Cray_5compiler_out.txt:              gfortran  + CrayMPI  on Cray XE6    Results: 8 / 8 / 8
BillLong_Cray_5compiler_out.txt:              pathscale + CrayMPI  on Cray XE6    Results: 8 / 8 / 8
BrianSmith-IBM_outlog-gcc.txt:                gfortran  + IBM-XL   on BGQ         Results: 8 / 8 / 8
JeffSquyres_OpenMP_linux-x86-64-gfortran.txt: gfortran  + OpenMPI  on x86-64      Results: 8 / 8 / 8
JeffSquyres_OpenMP_osx-x86-84-gfortran.txt:   gfortran  + OpenMPI  on osx-x86-64  Results: 8 / 8 / 8
Rajeev_gnu_laptop_out.txt:                    gfortran  + mpich2   on laptop      Results: 8 / 8 / 8
Rajeev_mpich_out.gfortran.x86-64.txt:         gfortran  + mpich2   on x86-64      Results: 8 / 8 / 8
mpi_align_Supalov_MPI3-Fortran.xlsx           gcc>=4.3.2+ IMPI     on IA64        Results: 8 / 8 / 8

E) No problems because all DOUBLE PRECISION alignments are identical = 4
 
Rajeev_mpich_out.gfortran.ia32.txt:           gfortran  + mpich2   on ia32        Results: 4 / 4 / 4
Rajeev_mpich_out.ifort.ia32.txt:              Intel     + mpich2   on ia32        Results: 4 / 4 / 4
mpi_align_Supalov_MPI3-Fortran.xlsx           Intel     + IMPI     on IA32        Results: 4 / 4 / 4
mpi_align_Supalov_MPI3-Fortran.xlsx           Intel     + IMPI     on IA64_32Bit  Results: 4 / 4 / 4
mpi_align_Supalov_MPI3-Fortran.xlsx           gcc 4.3.4 + IMPI     on IA32        Results: 4 / 4 / 4