| commit | 36b608cd6fbb9df4f0ebed12b13402e004f0a98a | |
| author | Mark Williams <mwilliams@fb.com> | |
| Thu, 23 Mar 2017 13:27:50 +0000 (23 06:27 -0700) | ||
| committer | Hhvm Bot <hhvm-bot@users.noreply.github.com> | |
| Thu, 23 Mar 2017 13:45:34 +0000 (23 06:45 -0700) | ||
| tree | 8c76c7c482bef7d64e897e8f28ce53365778283f | treesnapshot (tar.gz zip) |
| parent | ee50c3127978f9f3aa604231ae2c2cae8c3ada62 | commitdiff |
Add more function specific tracing
Summary:
hhbbc's --trace option can be used to specify a set of methods that
you want to trace, which can be useful when debugging issues in large
builds.
For my debugging, I found that the trace level (2) was not providing
enough information, and that I also needed to see what was going on in
cfg-opts, and dce.
Reviewed By: ricklavoie
Differential Revision: D4754778
fbshipit-source-id: 47fb5947a414c56d895b80aa1d9c17a241535e85
Summary:
hhbbc's --trace option can be used to specify a set of methods that
you want to trace, which can be useful when debugging issues in large
builds.
For my debugging, I found that the trace level (2) was not providing
enough information, and that I also needed to see what was going on in
cfg-opts, and dce.
Reviewed By: ricklavoie
Differential Revision: D4754778
fbshipit-source-id: 47fb5947a414c56d895b80aa1d9c17a241535e85
| hphp/hhbbc/analyze.cpp | diffblobblamehistory | |
| hphp/hhbbc/misc.h | diffblobblamehistory | |
| hphp/hhbbc/optimize.cpp | diffblobblamehistory |