On 2005-03-27, at 00:21, linux-os wrote:
Needless to say that there are enough architectures out there, which don't even have something like an explicit call as separate assembler instruction...Always, always, a call will be more expensive than a branch on condition. It's impossible to be otherwise. A call requires that the return address be written to memory (the stack), using register indirection (the stack-pointer).
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH] no need to check for NULL before calling kfree() -fs/ext2/
- From: linux-os <[email protected]>
- Re: [PATCH] no need to check for NULL before calling kfree() -fs/ext2/
- From: Horst von Brand <[email protected]>
- Re: [PATCH] no need to check for NULL before calling kfree() -fs/ext2/
- References:
- [PATCH] no need to check for NULL before calling kfree() - fs/ext2/
- From: Jesper Juhl <[email protected]>
- Re: [PATCH] no need to check for NULL before calling kfree() - fs/ext2/
- From: linux-os <[email protected]>
- Re: [PATCH] no need to check for NULL before calling kfree() - fs/ext2/
- From: Arjan van de Ven <[email protected]>
- Re: [PATCH] no need to check for NULL before calling kfree() -fs/ext2/
- From: linux-os <[email protected]>
- [PATCH] no need to check for NULL before calling kfree() - fs/ext2/
- Prev by Date: Re: INITRAMFS: junk in compressed archive
- Next by Date: Re: [PATCH] no need to check for NULL before calling kfree() -fs/ext2/
- Previous by thread: Re: [PATCH] no need to check for NULL before calling kfree() -fs/ext2/
- Next by thread: Re: [PATCH] no need to check for NULL before calling kfree() -fs/ext2/
- Index(es):
 |