Prior to this update, the rsh application was optimized through strict aliasing rules, even though it is not a performance-sensitive application. As a consequence, the GNU compiler collection (GCC) generated warning messages about breaking the strict-aliasing rules, despite correct functionality being the priority for rsh. With this update, strict aliasing has been disabled for rsh. Therefore, GCC now ignores the strict aliasing rules and no longer interrupts rsh processes with warning messages. However, this may also lead to a slight decrease in performance.
Description of problem:
Warnings about breaking strict aliasing rules in build.log
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Rebuild for RHEL-6.6
rshd.c:453: warning: dereferencing pointer 'second_connect.62' does break strict-aliasing rules
No such warnings
I guess toolchain, i.e. gcc, changed somehow. Let's play this safe and disable optimization. spec only change, add -fno-strict-aliasing to RPM_OPT_FLAGS.
VERIFIED rsh-0.17-64.el6.src.rpm @x86_64
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.