From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Edelsohn To: law AT cygnus.com Cc: Nick Ing-Simmons , mrs AT wrs.com, gcc AT gcc.gnu.org, mark AT codesourcery.com, rms AT gnu.org, jbuck AT synopsys.com Subject: Re: type based aliasing again Date: Wed, 15 Sep 1999 09:31:00 -0000 Message-id: <9909151630.AA36168@marc.watson.ibm.com> References: <13132.937411270@upchuck.cygnus.com> X-SW-Source: 1999-09/msg00631.html >>>>> Jeffrey A Law writes: Jeff> So are you going to propose next that we turn off automatic register allocation Jeff> because some programmers don't have enough of a clue to write correct code? Jeff> (yes, automatic register allocation will cause programs to behave in an Jeff> unexpected manner if the programmer does stupid things like not initializing Jeff> automatics, or not using volatile for variables live across setjmp). Jeff> Or are you going to propose that we turn off MEM_IN_STRUCT_P because some Jeff> clueless programmer violated the assumptions for that optimization? Jeff> Hell, while you're at it, you might as well turn off any optimization that Jeff> might have a bug. This is arguing by generalization and generalizing to the extreme. Different cases require different analysis and consideration. David From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Edelsohn To: law@cygnus.com Cc: Nick Ing-Simmons , mrs@wrs.com, gcc@gcc.gnu.org, mark@codesourcery.com, rms@gnu.org, jbuck@synopsys.com Subject: Re: type based aliasing again Date: Thu, 30 Sep 1999 18:02:00 -0000 Message-ID: <9909151630.AA36168@marc.watson.ibm.com> References: <13132.937411270@upchuck.cygnus.com> X-SW-Source: 1999-09n/msg00631.html Message-ID: <19990930180200.5IWG0Zwg6XNwr0kisiZreVAZfLq5xe5BxmV_gFbHtMg@z> >>>>> Jeffrey A Law writes: Jeff> So are you going to propose next that we turn off automatic register allocation Jeff> because some programmers don't have enough of a clue to write correct code? Jeff> (yes, automatic register allocation will cause programs to behave in an Jeff> unexpected manner if the programmer does stupid things like not initializing Jeff> automatics, or not using volatile for variables live across setjmp). Jeff> Or are you going to propose that we turn off MEM_IN_STRUCT_P because some Jeff> clueless programmer violated the assumptions for that optimization? Jeff> Hell, while you're at it, you might as well turn off any optimization that Jeff> might have a bug. This is arguing by generalization and generalizing to the extreme. Different cases require different analysis and consideration. David