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]

Re: what's required for builtin_memcpy to be inlined

To: jamie.lokier@cern.ch
Subject: Re: what's required for builtin_memcpy to be inlined
From: "Martin v. Loewis" <martin@mira.isdn.cs.tu-berlin.de>
Date: Fri, 10 Sep 1999 22:36:43 +0200
CC: skawina@geocities.com, gcc@gcc.gnu.org
References: <37D71694.631EF26D@geocities.com> <199909090826.KAA01101@mira.isdn.cs.tu-berlin.de> <19990910174426.B24439@pcep-jamie.cern.ch>

> The size is variable, but known by dataflow inference at compile time.
> I think GCC returns 1 from __builtin_constant_p in this case, nowadays.

It will do so only under optimization.

Martin

References:
- what's required for builtin_memcpy to be inlined
  - From: Artur Skawina
- Re: what's required for builtin_memcpy to be inlined
  - From: Martin v. Loewis
- Re: what's required for builtin_memcpy to be inlined
  - From: Jamie Lokier

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