Ebke, Hans-Christian <[EMAIL PROTECTED]> wrote: > So to resolve that problem I took the gcc 4.0.1 source code and patched > tree.h and tree-dump.c. The patched version introduces two new options for > -fdump-tree: The "parseable" option which produces unambiguous and easier to > parse but otherwise similar output to "raw" and the "maskstringcst" option > which produces output with the string constants masked since this makes > parsing the output even easier and I'm not interested in the string > constants.
You could write some code to escape special characters, so to write something like: @54 string_cst type: @61 strg: "wrong type:\n\0\0\xaf\x03\x03foo\"bar" lngt: 19 This would not need a different special option. -- Giovanni Bajo
