Large binary sizes
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 53
- Forks
- 27
- Avg merge
- 12d 22h
- Merged PRs (30d)
- 2
Description
Trieste executables are currently quite large, for example, on Ubuntu in Debug:
~/Trieste/build/dist$ tree -sh parsers
[4.0K] parsers
├── [ 13M] json_fuzzer
├── [ 13M] json_test
├── [ 22M] yamlc
├── [ 21M] yaml_fuzzer
└── [ 24M] yaml_test
~/Trieste/build/dist$ tree -sh infix
[4.0K] infix
├── [ 14M] infix
└── [ 13M] infix_trieste
Even in Release, they are larger than may be warranted (in particular, for infix):
~/Trieste/build/dist$ tree -sh parsers
[4.0K] parsers
├── [1.3M] json_fuzzer
├── [1.4M] json_test
├── [3.6M] yamlc
├── [3.6M] yaml_fuzzer
└── [3.8M] yaml_test
~/Trieste/build/dist$ tree -sh infix
[4.0K] infix
├── [1.5M] infix
└── [1.4M] infix_trieste
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the Debug and Release builds and the executable sizes in build/dist/parsers and build/dist/infix. Determine what reduction is appropriate for the listed binaries; done means the relevant executables are smaller without losing their current build outputs or behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100