On Mon, Jun 19, 2000 at 10:14:42AM +0200, John Hughes wrote:
> I don't want to sound dumb; but does anyone know *why* it's not inlining
> the memcpy? It used to.
Inlined memcpy can be very big in some cases, e.g. when gcc cannot
figure out the alignment of the target and destination pointers
at runtime and has to add misalignment handling code. In this case
it is faster to outline to save some L1 cache. gcc 2.96 got new
heuristics for that now.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jun 23 2000 - 21:00:16 EST