This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Fix PR middle-end/11151
- From: Mark Mitchell <mark at codesourcery dot com>
- To: Jim Wilson <wilson at specifixinc dot com>
- Cc: Eric Botcazou <ebotcazou at libertysurf dot fr>, gcc-patches at gcc dot gnu dot org
- Date: 17 Dec 2003 21:26:59 -0800
- Subject: Re: [PATCH] Fix PR middle-end/11151
- Organization: CodeSourcery, LLC
- References: <200311280955.46613.ebotcazou@libertysurf.fr> <3FCFE95E.7020900@specifixinc.com>
On Thu, 2003-12-04 at 18:11, Jim Wilson wrote:
> Eric Botcazou wrote:
> > This is the second part of the fix for this PR, which deals this time with
> > __builtin_return (the first part dealt with __builtin_apply).
>
> I think there is a historical error here allowing anyone to use
> __builtin_return. It was implemented for a specific purpose, to
> implement an Objective-C language feature. Allowing end users to use it
> however complicates the matter, becuase then, like any other language
> extension, we have to define how this interacts with all other language
> features, and it gets much more complicated than it was ever meant to
> be. I think the same is true for almost all builtin functions.
I agree.
There are very few builtins that should really be used by end-users
directly. (__builtin_constant_p and __builtin_expect are among the
likely exceptions.) I don't even think there are very many builtins
that should be used by "expert users" like glibc and the Linux kernel.
--
Mark Mitchell <mark@codesourcery.com>
CodeSourcery, LLC