= Project Name Compiler Flags on Pidora =<!-- Replace "Project Name" with the actual name of the project in the line above. -->
== Project Description ==
<!-- Description should be no longer than Find a paragraphset of compiler flags that reduce the binary size and improve performance for packages built for Pidora. Include links to any relevant on-line resources. For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. -->
== 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) Details ==
<!-- Name(s) Find a set of people casually working on the projectcompiler flags that creates smaller and more efficient binaries for Pidora, or who have contributed significant help. Include links compared to personal pages within wiki. Adding the names of your contributors here is a nice way to thank themcurrent compiler flags.
NOTE: only the Project Leader should add names here. You should not add your own name A set of packages will be selected for testing, to the Contributor listcover a range of dependencies and use cases, such as common utilities, libraries, and GUI tools. -->
== Project Details ==The packages will be built in a Mock environment on an ARMv6 machine.
<!-- 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 ==
=== 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 ===
<!-- Add links to any mentors or key participants in the community. -->TBD
=== Goals by Release ===
Goals for each release and plans for reaching those goals:
<!-- Note: Each student must have unique goals. These goals may be ''related'0.1' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella * Create a script that compiles a list of one project titlepackages from source, one student may work on packaging a piece using different combinations of software and another may work on documentationcompiler flags, or one may work on solving one bug and another on solving another bug, but two students must not work on outputs the same bug or depend on sizes of the other studentscompiled binaries* Find multiple combinations of compiler flags that create smaller binaries ''' work in order to be able to complete their own project0. -->2'''* Test the combinations found in 0.1against a larger set of packages to ensure there is a consistent reduction in binary size* Test the performance of the smaller binaries and determine which set of compiler flags yields the best performace '''0.23'''* 0.3Submit a patch to the rpm package recommending the new compiler flags
== Communication ==
=== Mailing Lists ===
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see httpFedora packaging: https://lists.fedoraproject.org -->/mailman/listinfo/packaging
=== Upsteam Wiki and Web ===
<!-- Links to upstream wikiRPM package: https:/web pages -->/admin.fedoraproject.org/pkgdb/acls/name/rpm
=== Links/Bugs/Tracking ===
=== Source Code Control ===
<!-- Add a link to source code URLs, including gitRPM package: http://mercurialpkgs.fedoraproject.org/svngit/cvs repositories -->rpm.git
=== Blogs ===
<!-- Links to the blogs of people involved, both inside and outside Seneca -->[http://cjiang13.wordpress.com/ Charley Jiang's Blog]
=== Non-Seneca Participants ===
