|
From: Julian S. <js...@ac...> - 2006-02-05 00:28:09
|
> Valgrind still has some nested functions in m_debuginfo/symtypes.c > (newvar and genstring). What's the policy with respect to nested > functions? Would you all be OK if I recoded this a little to remove the > nesting? I'd love to be rid of them. That'd be great, yes please. As far as I know they are the only thing standing in the way of being able to build V with icc, although that's based on experimentation from long ago. I don't know what level of gnuisms pathcc can cope with, but if it was also pathcc-buildable that would be good. The real issue is that we've had various regressions in debuginfo reading for non-gcc compilers because the test suite is only routinely built with gcc. So - technically - we could avoid such regressions by building the testsuite with non-gcc, but in general the wider the set of compilers that can build the whole thing successfully, the better, imo. Oh .. and the warnings bug me too. J |