зеркало из https://github.com/mozilla/gecko-dev.git
2b3a15afe9
We're planning on switching to IR-based profiling, so we can't use the frontend-based instrumentation to collect the order in which functions are executed...at least not during the build itself. Performance tests indicate that not having the order information decreases performance significantly. So we're going to check in static files for Win32 and Win64 and use those to perform the ordering. It's OK if these files are slightly out of date; as of this writing, builds that generate and then use these files complain that ~1/3 of the functions can't be found (!). We're just trying to do something slightly smarter than whatever the linker default is. Differential Revision: https://phabricator.services.mozilla.com/D31132 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| crashinjectdll | ||
| Makefile.in | ||
| __init__.py | ||
| autobinscope.py | ||
| crashinject.cpp | ||
| moz.build | ||
| mozconfig.vs-latest | ||
| mozconfig.vs2017 | ||
| orderfile.txt | ||
| pgomerge.py | ||