MAP...END MAP is something that I could not find a proper description of in the FTN95 documentation. I ended up consulting the Digital/Compaq Visual Fortran Language Reference Manual, http://jp.xlsoft.com/documents/intel/cvf/cvf_lref.pdf .
My guess is that FTN95 supports correct usage of MAP...END MAP, but a program that uses it improperly or leaves out essential syntax will behave in an unpredictable manner when compiled with FTN95.
Out of curiosity, I tried Lahey Fortran 95 7.10 on your original code, and received the following useful error messages:
jwd1600i-s 'su0.f90', line 1: No component defined in derived type definition for 'abcdefg'.
jwd1423i-s 'su0.f90', line 4: Only MAP declaration can appear in range of UNION declaration.
jwd1423i-s 'su0.f90', line 5: Only MAP declaration can appear in range of UNION declaration.
jwd1423i-s 'su0.f90', line 6: Only MAP declaration can appear in range of UNION declaration.
jwd1497i-s 'su0.f90', line 10, column 11: 'uvwx' not a component of a derived type, cannot be specified as structure component.
As we can see, Lahey F95 can be useful in getting the syntax correct in your code, following which you can return to FTN95.
Another finding, worth appreciating, perhaps: your example as well as my modification embed a non-standard F77 extended type component (UNION) inside an F90 Derived Type, and it works!