Difference between revisions of "ARMv8 Support Analysis"
(→Project Plan) |
(→Project Plan) |
||
| Line 57: | Line 57: | ||
<!-- Note: each contributor is expected to 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. --> | <!-- Note: each contributor is expected to 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 | ||
| − | + | ** Build initial script to identify assembly code inside fedora packages | |
* 0.2 | * 0.2 | ||
* 0.3 | * 0.3 | ||
Revision as of 11:41, 5 October 2012
Contents
ARMv8 Support Analysis
Project Description
Many Fedora packages contain assembley code for performance optimization or platform-specific support. Assembley code is very processor-specific. When assembley code is not present for a specific architecture, either the package will not build on that architecture, or other code (typically C) which is not processor-specific is used instead.
This project involves analyzing Fedora packages to determine which ones contain assembly code, and determining whether the package will probably build on the upcoming ARMv8 64-bit architecture.
Expected outcome: An analysis of part of the Fedora package set to predict ARMv8 build outcomes.
Maximum number of students: 6 (each taking part of the Fedora package set)
Skills required: packaging, scripting, writing
Resources: Chris Tyler (ctyler), Jon Masters (jonmasters)
Sources: ARMv8_Support_Analysis
Project Leader(s)
Alexander Davis
Wiki Page: Alexander Davis
IRC: Zulafoxx
Andrew Oatley-Willis
Wiki Page: Andrew OW
Learn: acoatley-willis
IRC: oatley
M A
Wiki Page: Max
Learn: mhabed
IRC: maxam
Project Contributor(s)
Project Details
Project Plan
Tracking mechanism (bugzilla, trac, github, ...):
Key contacts:
Goals for each release and plans for reaching those goals:
- 0.1
- Build initial script to identify assembly code inside fedora packages
- 0.2
- 0.3
