=1. Find your group in the [[#Package Lists by Group|list below]]. Select the same number of packages as you have people in your group (e.g., if there are two in your group, then pick two of the three packages). Add a package from the Spares list if necessary. If you are doing this lab and are not in class, chose two packages from the Spares list. 2. Obtain the source code for this software. You can find the upstream website and download it from there (or the corresponding code repository), or on a Fedora system, you can follow these steps (recommended):  fedpkg clone -a ''packagename'' cd ''packagename'' fedpkg prep cd ''packagename-version'' 3. For each package, identify:* The general purpose of the package.* The location of all assembly language code. Check for <code>asm()</code>, <code>__asm__</code>, and stand-alone files (<code>.s</code> or <code>.S</code> files).* The purpose of each assembly language fragment.* Whether the asm code was written for that software package, or* The architectures supported.* Fallbacks, if any, provided for other architectures, and the impact of using the fallback (lower performance, missing features, incorrect operation).* Your estimate of whether the package can be built on aarch64 in its current form, and how that build would compare to the x86_64 build in terms of features and performance. (Note: It may be useful to look at the %build section of the spec file, located in the directory in which you performed the ''fedpkg prep''). 4. Select one package to present to the class during the lab period. 5. Write a detailed blog post with your findings for two of your group's packages. Include examples of some of the asm code found. == Package Lists by Group ===