J.C. Pizarro wrote on 04/10/07 10:24: > By example, worth weigths, use's frecuencies, statistical data, ... of GIMPLE. > To debug the GIMPLE too.
That's kept separately. Pointer maps, hash tables... > How you debug the failed GIMPLE? Lots of debug_*() functions available. You also use -fdump-tree-... a lot. In the future, I would like us to be able to inject GIMPLE directly at any point in the pipeline to give us the illusion of unit testing.
