[llvm-commits] [llvm-gcc-4.2] r93821 - in /llvm-gcc-4.2/trunk/gcc: llvm-convert.cpp llvm-debug.cpp llvm-debug.h llvm-internal.h

[Stuart Hastings]

On Jan 19, 2010, at 12:49 AM, Duncan Sands wrote:

> Hi Stuart, thanks for doing this.  Is there any reasonable way
> of adding tests that check that block debug info is being output
> correctly?  If so, it would be good to add a few.

I'm sure something could be done with a mildly-toxic mixture of  
dwarfdump and egrep, but I don't know if dwarfdump is commonly  
available on all LLVM platforms.  (A quick Google check shows that  
dwarfdump has been ported to Windows, but offhand I don't know if LLVM  
even generates DWARF on Windows.)

It may be possible to write some "awesome" regular expressions to  
examine the resulting assembly file, but these are difficult to write,  
and I expect they would break often as LLVM evolves.

I'm pretty sure that the GDB test suite already does testing for  
lexical blocks.  This is probably the best existing lexical block test  
we have.

What sort of testing did you have in mind?  How elaborate must this be?

stuart