This is both beneficial for the actual code and an enhancement wrt.
-ftrivial-auto-var-init as it gets rid of a usage of nsAutoCString.
Differential Revision: https://phabricator.services.mozilla.com/D187198
This is both beneficial for the actual code and an enhancement wrt.
-ftrivial-auto-var-init as it gets rid of a usage of nsAutoCString.
Differential Revision: https://phabricator.services.mozilla.com/D187198
This is both beneficial for the actual code and an enhancement wrt.
-ftrivial-auto-var-init as it gets rid of a usage of nsAutoCString.
Differential Revision: https://phabricator.services.mozilla.com/D187198
This is a best effort attempt at ensuring that the adverse impact of
reformatting the entire tree over the comments would be minimal. I've used a
combination of strategies including disabling of formatting, some manual
formatting and some changes to formatting to work around some clang-format
limitations.
Differential Revision: https://phabricator.services.mozilla.com/D13371
The only real way to get memory mapping information on Linux is to read and
parse /proc/self/maps, and infer information about a specific pointer based on
its contents.
This patch adds a helper which parses the entire contents of smaps, and
returns an array of objects describing each region. It also updates resident
unique reporter to use that helper. Later patches use it to map stack base
addresses to VM regions, and report their usage data.
MozReview-Commit-ID: 8VUu1kMT77L
The only real way to get memory mapping information on Linux is to read and
parse /proc/self/maps, and infer information about a specific pointer based on
its contents.
This patch adds a helper which parses the entire contents of smaps, and
returns an array of objects describing each region. It also updates resident
unique reporter to use that helper. Later patches use it to map stack base
addresses to VM regions, and report their usage data.
MozReview-Commit-ID: 8VUu1kMT77L
serge-sans-paille