On Thu, Oct 20, 2011 at 10:21:27AM +0200, Richard Guenther wrote: > I'd rather have a way to make dump-files more structured (so, following > some standard reporting scheme) than introducing yet another way > of output. [after making dump-files more consistent it will be easy > to revisit patches like this, there would be a natural general central > way to implement it]
I'm not sure to understand what more structured dump-files mean. Are you thinking of making them in XML or in JSON format (both requires some minimal structure). > So, please fix dump-files instead. I'm not sure to understand what that means, because I am not sure to grasp the intended meaning and roles of dump files (in particular, from a plugin point of view). And I'm not sure to understand what fixing them means. My incomplete understanding is that dump files are for any kind of GCC-debugging (or GCC-plugin-debuggging) output which any pass might feel useful, but that is probably too weak as a definition. Or are dump files something more precise that that? In particular, should a dump file contain textual descriptions of GCC data useful to its pass [e.g. some "input" representation], or only modified by that pass [e.g. some representation of the passe's "output" or side-effect]? Regards. -- Basile STARYNKEVITCH http://starynkevitch.net/Basile/ email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359 8, rue de la Faiencerie, 92340 Bourg La Reine, France *** opinions {are only mines, sont seulement les miennes} ***
