From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-90551-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 32767 invoked by alias); 2 Feb 2004 23:44:32 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 32750 invoked from network); 2 Feb 2004 23:44:31 -0000
Received: from unknown (HELO mail-out4.apple.com) (17.254.13.23)
  by sources.redhat.com with SMTP; 2 Feb 2004 23:44:31 -0000
Received: from mailgate2.apple.com (a17-128-100-204.apple.com [17.128.100.204])
	by mail-out4.apple.com (8.12.10/8.12.11) with ESMTP id i12NiVX3009338
	for <gcc@gcc.gnu.org>; Mon, 2 Feb 2004 15:44:31 -0800 (PST)
Received: from relay1.apple.com (relay1.apple.com) by mailgate2.apple.com
 (Content Technologies SMTPRS 4.3.6) with ESMTP id <T67834fb0f9118064cc748@mailgate2.apple.com>;
 Mon, 2 Feb 2004 15:44:29 -0800
Received: from [17.201.21.123] (stravinsky.apple.com [17.201.21.123])
	by relay1.apple.com (8.12.9/8.12.11) with ESMTP id i12NiCpW017505;
	Mon, 2 Feb 2004 23:44:13 GMT
In-Reply-To: <1DFC59D7-55BA-11D8-A1BE-003065A77310@apple.com>
References: <1DFC59D7-55BA-11D8-A1BE-003065A77310@apple.com>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <B3A179DA-55D9-11D8-9283-0003931B8A28@apple.com>
Content-Transfer-Encoding: 7bit
Cc: Diego Novillo <dnovillo@redhat.com>, GCC List <gcc@gcc.gnu.org>
From: Syd Polk <spolk@apple.com>
Subject: Re: Help restricting args of an intrinsic function
Date: Mon, 02 Feb 2004 23:44:00 -0000
To: Mike Stump <mrs@apple.com>
X-SW-Source: 2004-02/txt/msg00137.txt.bz2


On Feb 2, 2004, at 11:58 AM, Mike Stump wrote:
> On Saturday, January 31, 2004, at 07:25 AM, Diego Novillo wrote:
>> Syd seems to be looking for anything that the compiler can prove is a
>> constant.
>
> Ok, I'll buy that, but I don't think we want anything that can ever be 
> turned off via an -O style option, or anything that is (or can be) 
> machine dependent.
>

What we support needs to work at -O0.

>> Powerful != expensive.  Why are you considering such a simple data 
>> flow
>> problem a non-starter?
>
> We don't want to offer something that only compiles code on some 
> machine or only compiles code with certain optimization settings.
>
> The pointer case may be just beyond what we want to work.
>

I don't think that we will need the pointer case. We will need the 
following:

- hard-coded integers
- const int variables
- static const int members in C++
- enums

Anything else does not work in the competing compiler, either.

Syd Polk
Apple Computer
Technology EPM, Mac OS X Development Tools
+1 408 974-0577