From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Earnshaw To: David Edelsohn Cc: richard.earnshaw AT arm.com Subject: Re: type based aliasing again Date: Tue, 14 Sep 1999 10:10:00 -0000 Message-id: <199909141706.SAA08354@sun52.NIS.cambridge> References: <9909141656.AA20910@marc.watson.ibm.com> X-SW-Source: 1999-09/msg00545.html dje@watson.ibm.com said: > I think that -ffast-math and the behavior of compilers from other > vendors is good precedent that -fstrict-aliasing should be removed > from the standard -O# optimization levels and accessed orthogonally. -ffast-math doesn't give any precedent at all. -ffast-math enables optimizations that the relevant standards disallow. -fstrict-aliasing does exactly the opposite. Richard. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Earnshaw To: David Edelsohn Cc: richard.earnshaw@arm.com Subject: Re: type based aliasing again Date: Thu, 30 Sep 1999 18:02:00 -0000 Message-ID: <199909141706.SAA08354@sun52.NIS.cambridge> References: <9909141656.AA20910@marc.watson.ibm.com> X-SW-Source: 1999-09n/msg00545.html Message-ID: <19990930180200.2a--MAOq2wzmeCd1kj-OWaovQ4oZl0HMpArVZttC2U8@z> dje@watson.ibm.com said: > I think that -ffast-math and the behavior of compilers from other > vendors is good precedent that -fstrict-aliasing should be removed > from the standard -O# optimization levels and accessed orthogonally. -ffast-math doesn't give any precedent at all. -ffast-math enables optimizations that the relevant standards disallow. -fstrict-aliasing does exactly the opposite. Richard.