From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen To: craig AT jcb-sc.com Cc: ak AT muc.de, gcc AT gcc.gnu.org Subject: Re: type based aliasing again Date: Thu, 16 Sep 1999 22:19:00 -0000 Message-id: <19990917052118.A4170@fred.muc.de> References: <199909151655.RAA05716@tiuk.ti.com> <13132.937411270@upchuck.cygnus.com> <19990915170504.15439.qmail@deer> <19990916184913.21978.qmail@deer> X-SW-Source: 1999-09/msg00746.html On Thu, Sep 16, 1999 at 08:49:13PM +0200, craig@jcb-sc.com wrote: > >Because fixing it often needs major data structure changes (overlap -> > >explicit union), which are often just impossible to submit into a > >stable code freezed production release mainteance tree. Because of > >gcc's lack of anonymous unions in C it usually requires changes to > >every user of that possible overlapped data structure, it is not possible > >to encapsulate it. > > That's why we offer -fno-alias-analysis, which is going beyond > the strict mandate of an ISO C compiler to compile ISO C code. Apparently not. Or what was that MEM_IN_STRUCT_P thing that cannot be turned off again? Also gcc's first mandate is to compile GCC code. ISO C is only a option :) -A. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen To: craig@jcb-sc.com Cc: ak@muc.de, gcc@gcc.gnu.org Subject: Re: type based aliasing again Date: Thu, 30 Sep 1999 18:02:00 -0000 Message-ID: <19990917052118.A4170@fred.muc.de> References: <199909151655.RAA05716@tiuk.ti.com> <13132.937411270@upchuck.cygnus.com> <19990915170504.15439.qmail@deer> <19990916184913.21978.qmail@deer> X-SW-Source: 1999-09n/msg00746.html Message-ID: <19990930180200.fC_BdPZ7_429acQwQP0UlqOvo0bMt7EzQp9LUUhdb1Q@z> On Thu, Sep 16, 1999 at 08:49:13PM +0200, craig@jcb-sc.com wrote: > >Because fixing it often needs major data structure changes (overlap -> > >explicit union), which are often just impossible to submit into a > >stable code freezed production release mainteance tree. Because of > >gcc's lack of anonymous unions in C it usually requires changes to > >every user of that possible overlapped data structure, it is not possible > >to encapsulate it. > > That's why we offer -fno-alias-analysis, which is going beyond > the strict mandate of an ISO C compiler to compile ISO C code. Apparently not. Or what was that MEM_IN_STRUCT_P thing that cannot be turned off again? Also gcc's first mandate is to compile GCC code. ISO C is only a option :) -A.