On Thu, Sep 28, 2006 at 01:26:00PM +0200, Jan Beulich wrote:
> While I'm not certain whether gcc is able to split one function's code
> between different sections (if for nothing else, this might help reduce
> TLB pressure by moving code unlikely to be executed not just out of
Yes, and that caused
On Thu, 2006-09-28 at 13:26 +0200, Jan Beulich wrote:
> While I'm not certain whether gcc is able to split one function's code
> between different sections
Yes. See the -freorder-blocks-and-partition option, which can move code
to hot/cold sections.
> However, when frame unwind information is g
On Sep 28, 2006, at 4:26 AM, Jan Beulich wrote:
While I'm not certain whether gcc is able to split one function's
code between different sections
Kinda, sorta... Hot-cold partitioning (-freorder-blocks-and-
partition) does this. If one exposed a FE language construct to so
tag code, then
On Thu, Sep 28, 2006 at 01:26:00PM +0200, Jan Beulich wrote:
> To cover all cases, it would basically appear to be necessary to
> add a referral op to the set of DW_CFA_* ops, which would
> indicate that the frame state at the given point is to be derived
> by assuming the location counter would in
While I'm not certain whether gcc is able to split one function's code
between different sections (if for nothing else, this might help reduce
TLB pressure by moving code unlikely to be executed not just out of
the main function body), by way of inline assembly the Linux kernel
certainly does in ma
