H1 2015 Priorities and Bare-Metal Programming

[via Digitalmars-d]

On Tuesday, 3 February 2015 at 22:41:30 UTC, Jonathan M Davis 
wrote:
> Well, as far as I can tell, that's pretty much exactly what 
> Walter meant by
> "hot" and "cold" - how likely they are to be called, with the 
> idea that the
> compiler could then use that information to better optimize - 
> be it inlining
> or some other optimization.

But "hot" does not imply inlining. You might want to tell the 
compiler that a function should use "hot" function call mechanics 
and never inline (for pragmatic reasons, like injecting 
breakpoints).