On Wed, 10 May 2017, Jakub Jelinek wrote: > Can it at least be taken out of -fdump-tree-all? It is huge, often larger > than the sum of all the other dump files, and don't remember ever using it > for anything.
Yes, apart from advertising the capability I don't imagine it's useful to produce that dump without a special flag. > Instead of trying to write a parser for it and reconstructing > something you can then later analyze, isn't it better to just write a plugin > that can analyze it directly? I think I can understand people writing a parser when it's sufficient; it won't need to be recompiled for a specific compiler version (with headers from that compiler), won't crash the compiler if you did something wrong. For people more familiar with a dynamic language like Python than C/C++ it may be just more comfortable to do it that way. Alexander