| commit | 06109fa93975f94ac7763fcc2946343de90a0c8a | [log] [tgz] |
|---|---|---|
| author | spoon@google.com <spoon@google.com@8db76d5a-ed1c-0410-87a9-c151d255dfc7> | Mon Jul 06 22:03:31 2009 +0000 |
| committer | spoon@google.com <spoon@google.com@8db76d5a-ed1c-0410-87a9-c151d255dfc7> | Mon Jul 06 22:03:31 2009 +0000 |
| tree | 2ec0b155f0abdb18ff2c4f829643dcc9625f5fdd | |
| parent | a1fc730096d7cad794a4dee774bce78fcc3e8f71 [diff] |
Has SOYC show dependency information for all of the dependency graphs built and used by the code splitter. Thus, it is possible to debug why code ends up in any of the code fragments the compiler emits. Review by: kprobst git-svn-id: https://google-web-toolkit.googlecode.com/svn/trunk@5676 8db76d5a-ed1c-0410-87a9-c151d255dfc7