This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch]: cleanup more builtins 1/5-5/5
- From: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- To: roger at eyesopen dot com
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Sun, 3 Oct 2004 08:31:59 -0400 (EDT)
- Subject: Re: [patch]: cleanup more builtins 1/5-5/5
- References: <Pine.LNX.4.44.0410021425210.24025-100000@www.eyesopen.com>
> On some non-POSIX platforms, the system headers may prototype these
> functions as "char*", or "unsigned char*" (instead of "void*",
> which are considered close enough for GCC to continue to
> fold/expand the builtins.
I don't feel strongly about this, but I don't think that example ever
happens in practice. There's fixincludes hackery to change these
system decls into void*. Plus we no longer support any pre-ISO-C
systems, right? (Well maybe if you boot from an older gcc version...)
However, it occurs to me that we call expand_builtin_memmove from the
bcopy expander which has a return type of just `void'. So we should
probably honor that at least.
> I appreciate we're not exactly consistent with these semantics at the
> moment, but your patches 2/5 and 3/5 move us slightly further away
> from the ideal.
>
> I hope this sounds acceptable?
Sure. Will resubmit.
--Kaveh
--
Kaveh R. Ghazi ghazi@caip.rutgers.edu