Difference between revisions of "Compiler Flags on Pidora"

From CDOT Wiki
Jump to: navigation, search
(Project Details)
(Project Details)
Line 15: Line 15:
 
== Project Details ==
 
== Project Details ==
  
Find a set of compiler flags that builds smaller and more efficient packages for Pidora.
+
Find a set of compiler flags that creates smaller and more efficient binaries for Pidora, compared to the current compiler flags.
  
 
A set of packages will be selected for testing, to cover a range of dependencies and use cases, such as common utilities, libraries, and GUI tools.
 
A set of packages will be selected for testing, to cover a range of dependencies and use cases, such as common utilities, libraries, and GUI tools.

Revision as of 00:24, 10 October 2013

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

Charley Jiang

Project Contributor(s)

TBD

Project Details

Find a set of compiler flags that creates smaller and more efficient binaries for Pidora, compared to the current compiler flags.

A set of packages will be selected for testing, to 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

Communication

Mailing Lists

Upsteam Wiki and Web

Links/Bugs/Tracking

Source Code Control

Blogs

Charley Jiang's Blog

Non-Seneca Participants

Planets

Project News