This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: what's required for builtin_memcpy to be inlined
- To: rth at cygnus dot com (Richard Henderson)
- Subject: Re: what's required for builtin_memcpy to be inlined
- From: Joern Rennecke <amylaar at cygnus dot co dot uk>
- Date: Mon, 13 Sep 1999 18:28:08 +0100 (BST)
- Cc: skawina at geocities dot com, jamie dot lokier at cern dot ch, martin at mira dot isdn dot cs dot tu-berlin dot de, gcc at gcc dot gnu dot org
> On Fri, Sep 10, 1999 at 10:51:25PM +0200, Artur Skawina wrote:
> > [I'm not complaing that __builtin_constant_p got smarter -- that's
> > a very good thing in itself, and I hope it gets even smarter. It's
> > just that a __builtin_constant_p that is smarter then a builtin
> > string routine makes the latter much less useful...]
>
> Perhaps in the moderately near future we'll be able to do
> something about this. Nothing near-term though.
Well, wouldn't this depend on code contributions?
I think it should be faily straightforward to fold builtin function calls
when their arguments are constant.