← Back to context

Comment by jiggawatts

3 years ago

I revised my numbers a bit by filtering out the junk and focusing only on the code that most likely contributes to the runtime components (where the security risks lie). E.g.: Excluded the samples, test suites, doco, changelogs, etc... and kept mostly just the C/C++ and assembly code.

I also recompressed all of the libraries with identical settings to make the numbers more consistent.