This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: frame unwind issue with discontiguous code
- From: Mike Stump <mrs at apple dot com>
- To: Jan Beulich <jbeulich at novell dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 28 Sep 2006 12:56:41 -0700
- Subject: Re: frame unwind issue with discontiguous code
- References: <451BCD68.76E4.0078.0@novell.com>
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 the hot-cold partitioner could make use of that
information. Naturally, when complete, it would have to manage the
debug information and the unwind information. As I recall, it might
not be that complete yet.
I think exposing a language feature so that you can tell the compiler
to so split code would be better than trying to do it behind the
compiler's back.
If you profiled and tweaked and tuned, you might be able to get the
compiler to partition the code for you, though, having that sticky in
the source base so that everyone can just compile it, is well, a dream.