Trim/inspect the size of CT-related symbols |
|||||
Issue descriptionAccording to mef@ in https://bugs.chromium.org/p/chromium/issues/detail?id=663883, not having CT-related symbols linked in decreases the binary size by ~50K. This is considered a large size for CT code, we should: (!) look into trimming the code. (2) enabling more linker optimizations for this code (for example, net::ct::HashAlgorithmToString shouldn't be linked in unless the SCT information is to be printed to somewhere).
,
Nov 17 2016
I've only tried it with cronet builds for iOS.
Those builds require chromium checkout on Mac OS.
Building Cronet framework should be as easy as running the following command from chromium checkout:
components/cronet/tools/package_ios.py -g out/Framework
I've used the following command to generate list of symbols without offsets, but there could be a better way:
symbols -noSources out/Framework/Release-iphoneos/Cronet.framework/Cronet | awk '{$1=""; print $0}'
,
Nov 18 2016
,
Oct 31 2017
,
Nov 1 2017
If this would help us avoid Issue 593051, that would be awesome and I'd consider this effort much higher priority.
,
Nov 2 2017
Paul: With respect to Issue 593051, that's not related to CT. That is, the crash would simply move to some other stack, because it's something clobbering the memory.
,
Nov 2
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 3
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by rsleevi@chromium.org
, Nov 17 2016