Difference between revisions of "Compiler Flags on Pidora"

From CDOT Wiki
Jump to: navigation, search
(Created page with '= Project Name = <!-- Replace "Project Name" with the actual name of the project in the line above. --> == Project Description == <!-- Description should be no longer than a pa…')
 
Line 1: Line 1:
−
= Project Name =
+
= Compiler Flags on Pidora =
−
<!-- Replace "Project Name" with the actual name of the project in the line above. -->
 
  
 
== Project Description ==
 
== Project Description ==
  
−
<!-- Description should be no longer than a paragraph. Include links to any relevant on-line resources. For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. -->
+
Find a set of compiler flags that reduce the binary size and improve performance for packages built for Pidora.
  
 
== Project Leader ==
 
== Project Leader ==
  
−
<!-- Name(s) of primary person working on the project.
+
[[User:Charley Jiang | Charley Jiang]]
  
−
If there is more than one person working on related projects, they must have separate project pages, and the project title and description should identify who is doing what. For example:
+
== Project Contributor(s) ==
  
−
Include links to personal pages within wiki and to blog sites. -->
+
TBD
  
−
== Project Contributor(s) ==
+
== Project Details ==
  
−
<!-- Name(s) of people casually working on the project, or who have contributed significant help. Include links to personal pages within wiki. Adding the names of your contributors here is a nice way to thank them.
+
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.
  
−
NOTE: only the Project Leader should add names here. You should not add your own name to the Contributor list. -->
+
The packages will be built in a Mock environment on an ARMv6 machine.
−
 
 
−
== Project Details ==
 
  
−
<!-- Provides more depth than the Project Description. This is the place for technical discussions, project specs, or other details. If this gets very long, you might consider breaking this part into multiple pages and linking to them. -->
+
'''List of packages'''
 +
* TBD
  
 
== Project Plan ==
 
== Project Plan ==
  
 
=== Tracking ===
 
=== Tracking ===
−
<!-- Describe the tracking mechanisms you are using for your project (bugzilla, trac, github, ...) -->
+
Project updates will be posted to this page and [http://cjiang13.wordpress.com/ Charley's Blog]
  
 
=== Key contacts ===
 
=== Key contacts ===
−
<!-- Add links to any mentors or key participants in the community. -->
+
TBD
  
 
=== Goals by Release ===
 
=== Goals by Release ===
  
 
Goals for each release and plans for reaching those goals:
 
Goals for each release and plans for reaching those goals:
−
<!-- Note: Each student must have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. -->
+
 
 
* 0.1
 
* 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
 
* 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
 
* 0.3
 +
** Modify .rpmmacros file and submit for approval
  
 
== Communication ==
 
== Communication ==
Line 55: Line 68:
  
 
=== Blogs ===
 
=== Blogs ===
−
<!-- Links to the blogs of people involved, both inside and outside Seneca -->
+
[http://cjiang13.wordpress.com/ Charley Jiang's Blog]
  
 
=== Non-Seneca Participants ===
 
=== Non-Seneca Participants ===

Revision as of 18:08, 7 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

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

Communication

Mailing Lists

Upsteam Wiki and Web

Links/Bugs/Tracking

Source Code Control

Blogs

Charley Jiang's Blog

Non-Seneca Participants

Planets

Project News

Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=Compiler_Flags_on_Pidora&oldid=99986"