Generated C++ Code breaks gcc's strict aliasing rules

Hi everyone,

I am using RTI's C++ mapping with a recent gcc and g++ -O2 or -O3. I am getting a lot of warnings because some of the RTI code breaks strict-aliasing rules:

/home/user/src/mycode/generated/Foo.cxx:323:14: note: in expansion of macro 'RTICdrStream_serializeFloat'
         if (!RTICdrStream_serializeFloat(
              ^
/opt/rti_connext_dds-5.2.0/include/ndds/cdr/cdr_stream_impl.h:472:55: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
       *(RTICdr4Byte *)((me)->_currentPosition) = (*(in)), \
                                                       ^
/opt/rti_connext_dds-5.2.0/include/ndds/cdr/cdr_stream_impl.h:709:43: note: in expansion of macro 'RTICdrStream_serialize4ByteFastMacro'
   #define RTICdrStream_serialize4ByteFast RTICdrStream_serialize4ByteFastMacro
                                           ^
/opt/rti_connext_dds-5.2.0/include/ndds/cdr/cdr_stream_impl.h:1242:7: note: in expansion of macro 'RTICdrStream_serialize4ByteFast'
      (RTICdrStream_serialize4ByteFast((me), (const RTICdr4Byte *)(in)), \
       ^
/opt/rti_connext_dds-5.2.0/include/ndds/cdr/cdr_stream_impl.h:1401:39: note: in expansion of macro 'RTICdrStream_serialize4Byte'
   #define RTICdrStream_serializeFloat RTICdrStream_serialize4Byte
                                       ^

This is a problem in several ways:

• With a lot of IDL files, there are a lot of these warnings cluttering up the compiler output.
• Breaking the strict-aliasing rules can turn out to be a huge problem in practice because the compiler may end up producing unsafe code optimizations.

So my questions are:

• Is there any sort of guarantee that this will notlead to any problems in practice? I.e., is it truly safe to disable the warning?
• Do you have any plans or suggestions to improve the code?

Thanks in advance.