{"success":1,"onion":[{"id":"2775208","titolo":"\n      #2915 (Explore options to reduce binary size of Tor)\n     \u2013 Tor Bug Tracker & Wiki\n    ","ricetta":"[Online \/ ] #2915 (Explore options to reduce binary size of Tor)\n\u2013 Tor Bug Tracker & Wiki\nLoginPreferencesHelp\/GuideAbout TracRegisterForgot your password?\nView TicketsTimelineWikiTags\nContext Navigation\n\u2190 Previous TicketNext Ticket \u2192\nOpened 7 years ago\nLast modified 5 months ago\n#2915\nnew\nenhancement\nExplore options to reduce binary size of Tor\nReported by:\nSebastian\nOwned by:\nPriority:\nLow\nMilestone:\nTor: unspecified\nComponent:\nCore Tor\/Tor\nVersion:\nSeverity:\nNormal\nKeywords:\ntor-client, modularity, download-size, memory, sponsor8-maybe, 034-triage-20180328, 034-removed-20180328\nCc:\nerinn\nActual Points:\nParent ID:\nPoints:\nReviewer:\nSponsor:\nSponsor8-can\nDescription\nOur bundles are pretty big, so we could benefit from \"free\" optimizations of binary size (those that don't incur a performance hit). Experimentation with ld's -deadcode flag (OS X) or -ffunction-sections, -fdata-sections together with -gc-sections have led to space savings of up to 25%, which seems well worthwhile.\nChild Tickets\nOl...","url":"http:\/\/ea5faa5po25cf7fb.onion\/projects\/tor\/ticket\/2915"}]}