On Sun, Jan 12, 2003 at 05:07:19PM -0500, Rob Wilkens wrote:
> In the case of an inline function, you're saving a jump, because the
> code that you would "goto" is right there in sequence with the code you
> are executing as far as the processor is concerned. In essence, you're
> duplicating code, but you're not retyping code, and your keeping code
> consistent accross all uses of it (keeping it modular).
These are usually error conditions. If you inline them, you will have
to jump *over* them as part of the normal code path. You don't save
any instructions, and you end up with a kernel which has much more
duplicated code and thus thrashes the cache more. It also makes the
code harder to read. goto makes it easy "stack" error handlers and not
worry about the order in which you do clean up.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jan 15 2003 - 22:00:42 EST