Difference between revisions of "Compiler Flags on Pidora"
(→Project Plan) |
|||
| Line 34: | Line 34: | ||
Goals for each release and plans for reaching those goals: | Goals for each release and plans for reaching those goals: | ||
| − | * 0.1 | + | '''* 0.1''' |
| + | |||
Option A: | Option A: | ||
| − | + | * Choose a set of packages to use for the duration of this project. | |
| − | + | * Find combinations of compiler flags that reduce the binary size compared to the current flags | |
Option B: | Option B: | ||
| − | + | * Choose a set of packages to optimize | |
| − | + | * Find a set of compiler flags that provide the best binary size and performance optimizations for those packages | |
| − | * 0.2 | + | '''* 0.2''' |
Option A: | Option A: | ||
| − | + | * Test the compiler flag combinations found in 0.1 for performance to determine most optimal flags | |
Option B: | Option B: | ||
| − | + | * Using the compiler flags from 0.1, test against a variety of other packages to prove optimization | |
| − | * 0.3 | + | '''* 0.3''' |
| − | + | * Modify .rpmmacros file and submit for approval | |
== Communication == | == Communication == | ||
Revision as of 19:09, 7 October 2013
Contents
Compiler Flags on Pidora
Project Description
Find a set of compiler flags that reduce the binary size and improve performance for packages built for Pidora.
Project Leader
Project Contributor(s)
TBD
Project Details
A set of packages will be selected to use for testing. Ideally, these packages will cover a range of dependencies and use cases, such as common utilities, libraries, and GUI tools.
The packages will be built in a Mock environment on an ARMv6 machine.
List of packages
- TBD
Project Plan
Tracking
Project updates will be posted to this page and Charley's Blog
Key contacts
TBD
Goals by Release
Goals for each release and plans for reaching those goals:
* 0.1
Option A:
- Choose a set of packages to use for the duration of this project.
- Find combinations of compiler flags that reduce the binary size compared to the current flags
Option B:
- Choose a set of packages to optimize
- Find a set of compiler flags that provide the best binary size and performance optimizations for those packages
* 0.2 Option A:
- Test the compiler flag combinations found in 0.1 for performance to determine most optimal flags
Option B:
- Using the compiler flags from 0.1, test against a variety of other packages to prove optimization
* 0.3
- Modify .rpmmacros file and submit for approval
