Messages in this thread | | | Date | Fri, 18 May 2007 23:50:33 -0400 | From | Jeff Garzik <> | Subject | Re: aio is unlikely |
| |
Nick Piggin wrote: > Aside from using branch constructs or hints that help the predictor > guess the right way... I think gcc will move unlikely paths right past > the end of the "likely" fastpath, so it can increase code size and be > somewhat suboptimal in terms of icache usage.
Thanks for the reminder. GCC definitely does code movement.
ISTR the code movement might even be "extreme", once the unit-at-a-time support arrived, placing "cold" code at the end of the compiled module.
Jeff
- 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/
| |