Differences

This shows you the differences between two versions of the page.

--- spo600:2024_summer_project [2024/06/19 11:36] – chris
+++ spo600:2024_summer_project [2024/08/19 07:14] (current) – chris
@@ Line 117: / Line 117: @@
 | 7 | Diagnostic Output | Provide diagnostic output (when activated by -fdump-...-... command-line options). |  | Anatolii Hryhorzhevskyi |
 | 8 | Git Wrangler | Mangage the repository. | This task includes rebasing as upstream changes and managing code reviews. | Rigels Hasani |
-| 9 | Update Documentation 1| Update the existing GCC IFUNC and FMV documentation (all archs) | Technical writing. | Shubh Janis |
+| 9 | Update Documentation 1| Update the existing GCC IFUNC and FMV documentation (all archs) | Technical writing. | Shubh Jani |
 | 10 | Create AFMV Documentation | Create documentation for the AFMV feature. | Technical writing. | Humaira Shaikh |
 | 11 | Create Tests | Create a suite of tests for the AFMV capability. (This is in addition to individual tests that the various task owners will prepare). | Requires understanding the existing test framework and writing tests. | Zijun Li |
@@ Line 181: / Line 181: @@
   * Integrate your code with any related code
   * Test and document what you've done
+The goal is to get a working proof-of-concept of the GCC AFMV feature; please keep this in mind as you prioritize your work!
+[[https://github.com/seneca-cdot/gcc|Class code repository]]:
+  * Minimum: your branch must include your code
+  * Target: your code is merged with the other compatible branches and is available in the master branch of the Git repository
 This is a summary of the discussion that took place in the June 17th class regarding status and next steps for each task:
@@ Line 197: / Line 203: @@
 ||11|Create Tests|Zijun Li|???|1, (2?), 4, (5/6?), 7)| | |Update with code changes| | Create a suite of tests for the AFMV capability. (This is in addition to individual tests that the various task owners will prepare).|$
 ||12|Test AFMV Implementation| | | | | | | | Use the existing test suite(s) to verify that the aarch64 changes are not introducing regressions on aarch64 or x86-64.|$
+=== Blogging ===
+  * Provide an overview of the final state of your project code:
+    * Location in class Git repository (branch)
+    * Integration with other branches
+    * What works, what limitations exist, what doesn't work, and what is not tested
+  * Provide detailed reflections on the project work and the course
 ==== Due Date ====
-  * June 15 for Stage 3
+  * June 21 for Stage 3