Difference between revisions of "ARMv8 Support Analysis"
(→Project Leader(s)) |
(→Project Description) |
||
| Line 15: | Line 15: | ||
Resources: Chris Tyler (ctyler), Jon Masters (jonmasters) | Resources: Chris Tyler (ctyler), Jon Masters (jonmasters) | ||
| − | Sources: [[SBR600_Potential_Projects#ARMv8_Support_Analysis|ARMv8_Support_Analysis]] | + | Sources: [[DPI908/SBR600_Potential_Projects#ARMv8_Support_Analysis|ARMv8_Support_Analysis]] |
<!-- 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]. --> | <!-- 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]. --> | ||
Revision as of 11:47, 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)
Andrew Oatley-Willis
Wiki Page: Andrew OW
Learn: acoatley-willis
IRC: oatley
M A
Wiki Page: Max
Learn: mhabed
IRC: maxam
Alexander Davis
Wiki Page: Alexander Davis
IRC: Zulafoxx
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
