Re: [FYI] Inlining support, rough patch

[Daniel Jacobowitz <drow@false.org>]

On Fri, Jun 13, 2008 at 11:27:54AM -0400, Daniel Jacobowitz wrote:
> Enjoy.

Forgot one thing I meant to add.

There are several test cases in the patch.  These have been very
useful while developing it; I've run them on five architectures and a
variety of compiler versions.  I didn't fix all the failures on some
of those versions.

I'm not sure what to do with them.  They're really hard to maintain at
no failures; every time you change one of the tests to fix a failure
on one platform, you run a higher than usual risk of breaking it on
another platform.  Tested for optimized code behavior are hard :-(

Also, I did test it on non-toy programs, obviously.  It does a
passibly good job stepping through the dwarf2 reader.  But the
behavior is a little quirky, especially due to scheduling.  And GDB is
very sensitive to compiler debug info bugs.  And GCC has a lot of
them.  Overall, with this patch merged I think the next places to
go for optimized code debugging are the two GCC branches currently
testbeds for improved optimized debug info generation.  After that,
it's back to the age-old debugging scheduled code problem.

-- 
Daniel Jacobowitz
CodeSourcery