This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Help restricting args of an intrinsic function

From: Richard Henderson <rth at redhat dot com>
To: Syd Polk <spolk at apple dot com>
Cc: Mike Stump <mrs at apple dot com>, Diego Novillo <dnovillo at redhat dot com>, GCC List <gcc at gcc dot gnu dot org>
Date: Mon, 2 Feb 2004 15:56:49 -0800
Subject: Re: Help restricting args of an intrinsic function
References: <1DFC59D7-55BA-11D8-A1BE-003065A77310@apple.com> <B3A179DA-55D9-11D8-9283-0003931B8A28@apple.com>

On Mon, Feb 02, 2004 at 03:44:11PM -0800, Syd Polk wrote:
> 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

Point the second should be for C++ only, where it has integer
constant expression semantics.

At which point, you're in EXACTLY the same situation that already
exists for x86 and altivec intrinsics.  This is not a new problem,
and it does not need a new solution.

r~

Follow-Ups:
- Re: Help restricting args of an intrinsic function
  - From: Syd Polk

References:
- Re: Help restricting args of an intrinsic function
  - From: Mike Stump
- Re: Help restricting args of an intrinsic function
  - From: Syd Polk

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]