From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Edelsohn To: Joe Buck Cc: mark@codesourcery.com (Mark Mitchell), gcc@gcc.gnu.org, rms@gnu.org Subject: Re: type based aliasing again Date: Thu, 30 Sep 1999 18:02:00 -0000 Message-ID: <9909090249.AA43518@marc.watson.ibm.com> References: <199909090223.TAA21727@atrus.synopsys.com> X-SW-Source: 1999-09n/msg00324.html Message-ID: <19990930180200.brd299DdEKDh6NJngRbfMkvjhxlNzx2PBUEFlEQSr8U@z> >>>>> Mark Mitchell writes: Mark> The compiler should continue to aggressively break code that Mark> misbehaves in this way. >>>>> Joe Buck writes: Joe> This is a philosophical issue. If you change "break" to "warn about" Joe> I could go along, but some users may be depending on code that they Joe> cannot fix immediately. A user who cannot fix his or her code immediately can use -fno-strict-aliasing, right? I think that GCC should continue to aggressively optimize code, including code that mis-behaves. If we can do a better job of warning than other commercial compilers that support aliasing optimizations, then we truly have a unique and beneficial features which helps users and gives GCC an advantage. David