This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Help restricting args of an intrinsic function
- From: Syd Polk <spolk at apple dot com>
- To: Mike Stump <mrs at apple dot com>
- Cc: Diego Novillo <dnovillo at redhat dot com>, GCC List <gcc at gcc dot gnu dot org>
- Date: Mon, 2 Feb 2004 15:44:11 -0800
- Subject: Re: Help restricting args of an intrinsic function
- References: <1DFC59D7-55BA-11D8-A1BE-003065A77310@apple.com>
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