Andi, On Thu, 08 Jun 2006, Andi Kleen wrote: > > Nothing on x86-64 at least - it uses -fno-reorder-blocks by default. > Why is that? --brian - 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] use unlikely() for current_kernel_time() loop
- From: Andi Kleen <[email protected]>
- Re: [PATCH] use unlikely() for current_kernel_time() loop
- References:
- [PATCH] use unlikely() for current_kernel_time() loop
- From: Andreas Dilger <[email protected]>
- Re: [PATCH] use unlikely() for current_kernel_time() loop
- From: Andi Kleen <[email protected]>
- Re: [PATCH] use unlikely() for current_kernel_time() loop
- From: Andrew Morton <[email protected]>
- Re: [PATCH] use unlikely() for current_kernel_time() loop
- From: Andi Kleen <[email protected]>
- [PATCH] use unlikely() for current_kernel_time() loop
- Prev by Date: Re: [PATCH] ide-cd: use blk_get_request()
- Next by Date: [PATCH -rt] Trivial compiler warning fix
- Previous by thread: Re: [PATCH] use unlikely() for current_kernel_time() loop
- Next by thread: Re: [PATCH] use unlikely() for current_kernel_time() loop
- Index(es):
 |