From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1967 invoked by alias); 25 Jan 2002 16:35:48 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 1898 invoked from network); 25 Jan 2002 16:35:42 -0000 Received: from unknown (HELO dberlin.org) (64.246.6.106) by sources.redhat.com with SMTP; 25 Jan 2002 16:35:42 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by dberlin.org (8.11.6/8.11.6) with ESMTP id g0PGZUn31908; Fri, 25 Jan 2002 11:35:35 -0500 Date: Fri, 25 Jan 2002 08:54:00 -0000 From: Daniel Berlin To: Robert Dewar cc: gcc@gcc.gnu.org, Subject: Re: g++ and aliasing bools In-Reply-To: <20020125161103.3F2CEF28D1@nile.gnat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-01/txt/msg01645.txt.bz2 On Fri, 25 Jan 2002, Robert Dewar wrote: > < relationships between C++ types, that may-alias is always determinable > statically correctly, or that we always correctly determine that we can't > determine it (IE never claim wrong that things may not alias). > I've said before, and i'll say again, that i'm not going to do that. > >> > > THat's fine, but the fact that you are not going to do it does not mean > that it is not desirable or not necessary! But it's *not* necessary when we've restricted ourselves to a subset of C++ structs and classes that correspond to C structs and classes!