Related articles |
---|
Register pressure and inlining linuxkaffee_@_gmx.net (Stephan Ceram) (2008-11-08) |
Re: Register pressure and inlining jeremy.wright@microfocus.com (Jeremy Wright) (2008-11-09) |
Re: Register pressure and inlining liangkun1983@gmail.com (Alex L.K) (2008-11-12) |
Re: Register pressure and inlining armelasselin@hotmail.com (Armel) (2008-11-12) |
Re: Register pressure and inlining bear@sonic.net (Ray Dillinger) (2008-11-12) |
Re: Register pressure and inlining cdg@nullstone.com (Christopher Glaeser) (2008-11-12) |
Re: Register pressure and inlining wimbleweather@verizon.net (Bob Morgan) (2008-12-17) |
From: | Jeremy Wright <jeremy.wright@microfocus.com> |
Newsgroups: | comp.compilers |
Date: | Sun, 9 Nov 2008 12:30:37 +0000 (UTC) |
Organization: | Compilers Central |
References: | 08-11-036 |
Keywords: | registers, optimize |
Posted-Date: | 09 Nov 2008 12:46:54 EST |
I can think of two ways extra spilling could occur.
Firstly - in a more complex example, your spill code might not be
optimally placed. In particular your spiller might not be
sophisticated enough to do live range splitting, and put the spill
code in the same place that the register save and restores would have
been originally.
Secondly - the compiler might (and probably should) do extra optimisation
passes after inlining. This could lead to further redundancy elimination
due to the improved information, which would then lead to extra register
pressure.
Jeremy Wright
Compiler Team Leader
Micro Focus
Return to the
comp.compilers page.
Search the
comp.compilers archives again.