Skip to content

Commit 3210617

Browse files
updates
1 parent 67e9cbb commit 3210617

File tree

2 files changed

+9
-9
lines changed

2 files changed

+9
-9
lines changed

content/learning-paths/cross-platform/adler32/build-6.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -6,14 +6,14 @@ weight: 6
66
layout: learningpathall
77
---
88

9-
## How can I test the build and run?
9+
## How can I build and run the test program?
1010

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.
1515

16-
Copy the information below to your GitHub Copilot Agent session:
16+
Paste the following prompt into your GitHub Copilot Agent session:
1717

1818
```console
1919
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
5757
5858
```
5959

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.
6161

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.

content/learning-paths/cross-platform/adler32/makefile-5.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ layout: learningpathall
88

99
## How can I create a Makefile to build and run the test program?
1010

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.
1212

1313
```console
1414
Read the .c files in my project and

0 commit comments

Comments
 (0)