On Mon, Jul 29, 2013 at 6:13 PM, Jonathan S. Shapiro <[email protected]>wrote:
> > - *Every* correct procedure return site *must* wrap the return with an > error code check, if only to propagate the possible error. The total number > of source lines of code is approximately doubled by this requirement, and a > great many forward-not-taken (therefore mispredicted) branches are > introduced into the code, with consequent maintenance errors and > performance costs. > > there are the gcc extensions that enable the likely/unlikely macros which sees use in this scenerio, as well as profile directed feedback which may be a more thumb friendly hammer http://kernelnewbies.org/FAQ/LikelyUnlikely
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
