You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/learning-paths/cross-platform/adler32/build-6.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,14 +6,14 @@ weight: 6
6
6
layout: learningpathall
7
7
---
8
8
9
-
## How can I test the build and run?
9
+
## How can I build and run the test program?
10
10
11
-
The required files are now complete to test the Adler32 algorithm.
12
-
-Adler32 C function
13
-
-Test program to call the Adler32 function to test for correctness and measure performance
14
-
- Makefile to build and run
11
+
You now have all the required files to test the Adler32 algorithm:
12
+
-A C implementation of the Adler32 function.
13
+
-A test program to verify correctness and measure performance.
14
+
-A Makefile to build and run the project.
15
15
16
-
Copy the information below to your GitHub Copilot Agent session:
16
+
Paste the following prompt into your GitHub Copilot Agent session:
17
17
18
18
```console
19
19
Use the Makefile to build the project and run to make sure the checksum results are correct for all data sizes.
@@ -57,6 +57,6 @@ The results confirm that your Adler-32 checksum implementation is correct for al
57
57
58
58
```
59
59
60
-
The results from GitHub Copilot explain that the Adler32 checksum calculations are correct and give some initial performance results. The results don't mean much yet as there is nothing to compare with.
60
+
The results from GitHub Copilot confirm that the Adler32 checksum calculations are correct and provide initial performance benchmarks. These results offer a solid baseline, but a meaningful comparison requires an optimized implementation.
61
61
62
-
Continue to the next section to implement Adler32 using NEON and compare the performance.
62
+
In the next section, you’ll implement Adler32 using NEON intrinsics and compare its performance against this baseline.
Copy file name to clipboardExpand all lines: content/learning-paths/cross-platform/adler32/makefile-5.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ layout: learningpathall
8
8
9
9
## How can I create a Makefile to build and run the test program?
10
10
11
-
To create a Makefile, copy and paste the information below to GitHub Copilot. The prompt explains that the Makefile should use`gcc`as the compiler and target the Neoverse N1 processor.
11
+
Paste the following prompt into GitHub Copilot. It tells Copilot to generate a Makefile that uses`gcc` and targets the Neoverse N1 processor for optimized performance.
0 commit comments