Messages in this thread | | | Date | Fri, 1 Jun 2007 00:33:22 +0200 | From | Andi Kleen <> | Subject | Re: [patch 9/9] Scheduler profiling - Use conditional calls |
| |
> I see your point, but there is a level of control on the branch I would > lack by doing so: the ability to put the call in either the if or else > branch. It is an optimization on i386.
What does it optimize exactly?
> Also, I live in the expectation that, someday, the gcc guys will be nice > enough to add some kind of support for a nop-based jump that would > require code patching to put a jump instead. If it ever happens, my > macro could evolve into this for newer compiler versions, which I could > not do with the if() statement you are proposing.
If that ever happens we couldn't use it anyways because Linux still has to support old compilers for a long time. And when those are dropped the code could be updated.
-Andi - 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/
| |