From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Ing-Simmons To: law AT cygnus.com Cc: mrs AT wrs.com, gcc AT gcc.gnu.org, mark AT codesourcery.com, rms AT gnu.org, dje AT watson.ibm.com, jbuck AT synopsys.com Subject: Re: type based aliasing again Date: Wed, 15 Sep 1999 08:02:00 -0000 Message-id: <199909151501.QAA26239@tiuk.ti.com> References: <2320.937209389@upchuck.cygnus.com> X-SW-Source: 1999-09/msg00620.html Jeffrey A Law writes: > In message < 199909130757.DAA05910@psilocin.gnu.org >you write: > > Changing the default to -fno-strict-aliasing would certainly solve the > > immediate problem. If people are happy with that, as a more or less > > permanent decision, I think it avoids most of the need to do anything > > else. (An added warning might be desirable, though, even with > > -fno-strict-aliasing.) >I strongly feel this is the wrong approach. > >It penalizes those programmers who write correct code to cater to the >programmers that do not write correct code. No, it allows _programmers_ that know what they are doing to get the benefit of their knowledge by the simple expedient of adding -fstrict-aliasing to Makefile.in and forgetting about it. While protecting sys-admins and users of open-source products that just build but do not write them from the bad habits that not-so-good/or too-clever-for-their-own-good programmers have developed over the decades. -- Nick Ing-Simmons Via, but not speaking for: Texas Instruments Ltd. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Ing-Simmons To: law@cygnus.com Cc: mrs@wrs.com, gcc@gcc.gnu.org, mark@codesourcery.com, rms@gnu.org, dje@watson.ibm.com, jbuck@synopsys.com Subject: Re: type based aliasing again Date: Thu, 30 Sep 1999 18:02:00 -0000 Message-ID: <199909151501.QAA26239@tiuk.ti.com> References: <2320.937209389@upchuck.cygnus.com> X-SW-Source: 1999-09n/msg00620.html Message-ID: <19990930180200.WmR8-Su6lLNZ1vzazV5DEb9iE5wm6YnaBro7hyB9rsE@z> Jeffrey A Law writes: > In message < 199909130757.DAA05910@psilocin.gnu.org >you write: > > Changing the default to -fno-strict-aliasing would certainly solve the > > immediate problem. If people are happy with that, as a more or less > > permanent decision, I think it avoids most of the need to do anything > > else. (An added warning might be desirable, though, even with > > -fno-strict-aliasing.) >I strongly feel this is the wrong approach. > >It penalizes those programmers who write correct code to cater to the >programmers that do not write correct code. No, it allows _programmers_ that know what they are doing to get the benefit of their knowledge by the simple expedient of adding -fstrict-aliasing to Makefile.in and forgetting about it. While protecting sys-admins and users of open-source products that just build but do not write them from the bad habits that not-so-good/or too-clever-for-their-own-good programmers have developed over the decades. -- Nick Ing-Simmons Via, but not speaking for: Texas Instruments Ltd.