Difference between revisions of "ARMv8 Support Analysis"
(→Project Leader(s)) |
(→Mailing Lists) |
||
| Line 62: | Line 62: | ||
=== Mailing Lists === | === Mailing Lists === | ||
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org --> | <!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org --> | ||
| + | {{fplist|devel}} | ||
=== Upsteam Wiki and Web === | === Upsteam Wiki and Web === | ||
Revision as of 10:48, 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: [[1]]
Project Leader(s)
Alexander Davis
Wiki Page: Alexander Davis
IRC: Zulafoxx
Andrew Oatley-Willis
Wiki Page: Andrew OW
IRC: oatley
M A
Wiki Page: Max
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
- 0.2
- 0.3
