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/more-11.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,11 +8,11 @@ layout: learningpathall
8
8
9
9
## What else can I do with GitHub Copilot on this project?
10
10
11
-
You can investigate more topics using GitHub Copilot.
11
+
GitHub Copilot can help you explore additional performance and optimization ideas:
12
12
13
-
-Direct GitHub Copilot to try different compiler flags and use Agent mode to iterate through the options to find the best solution.
14
-
- Add support for the Clang compiler to the Makefile and compare the results to GCC. Depending on the application code, changing the compiler can result in improved performance.
15
-
-Use GitHub Copilot to generate different data sizes and random data patterns to further investigate correct functionality and performance.
16
-
-Try different algorithm implementations that use compiler autovectorization instead of NEON intrinsics or break down the Adler32 checksum into smaller blocks of data. It may be possible to get even better performance without NEON using the compiler and a better structure for the C code.
13
+
-Test different compiler flags using Agent mode to automate iteration and identify the best combinations.
14
+
- Add Clang support to your Makefile and compare performance against GCC — performance can differ significantly depending on your code structure.
15
+
-Generate a wider range of data sizes and random patterns to stress-test functionality and measure performance under varied conditions.
16
+
-Explore alternative algorithm structures that rely on compiler autovectorization instead of NEON intrinsics — you might discover better performance simply by restructuring the C code.
17
17
18
-
While AI tools do not create performance code for every programming problem, they can be a big help to get you started in a new area of programming such as performance optimization using NEON intrinsics.
18
+
AI tools won’t always generate high-performance code out of the box, but they can rapidly accelerate your experimentation and learning — especially in new areas of programming like NEON-based performance optimization.
Copy file name to clipboardExpand all lines: content/learning-paths/cross-platform/adler32/summary-10.md
+14-3Lines changed: 14 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,9 @@ layout: learningpathall
10
10
11
11
You can use GitHub Copilot to generate a project summary in a README file.
12
12
13
-
Copy the prompt below to your GitHub Copilot Agent chat and review the created README file.
13
+
Use the prompt below to collaborate with GitHub Copilot Agent to generate your README.
14
+
15
+
Review and refine the results to align them with your project's goals.
14
16
15
17
```console
16
18
Review the files in my project.
@@ -20,7 +22,7 @@ Add a note that the performance results recorded on the Neoverse N1 processor.
20
22
Use a table to compare the original version and the NEON version and show the performance improvement factor.
21
23
```
22
24
23
-
Below is the created README.md file. The formatting doesn't match the Learning Path template exactly, but you can copy the the README file to a new repository in GitHub for improved results.
25
+
Below is the created README.md file. The formatting doesn't match the Learning Path template exactly, but you can copy the README file to a new repository in GitHub for improved results.
24
26
25
27
## Adler-32 Checksum Implementation Comparison
26
28
@@ -93,6 +95,15 @@ The table summarizes the speedup obtained by the NEON version.
93
95
94
96
Using Agent mode in GitHub Copilot is a significant benefit when you are actively building and running software. Agent mode can create files and modify them to make needed improvements.
95
97
96
-
The entire project was done without modifying any of the generated files. While you may not need to do this on a real project, the concept of writing NEON intrinsics to improve performance was demonstrated. You can also use GitHub Copilot to fix issues in NEON code that are difficult to debug for developers who are not experts.
98
+
### Tips for Using GitHub Copilot Effectively
99
+
100
+
This project was completed using GitHub Copilot Agent without modifying the generated files. While that might not be practical in every case, the demonstration shows how NEON intrinsics can significantly boost performance.
101
+
102
+
GitHub Copilot is especially useful for:
103
+
* Generating vectorized versions of scalar code.
104
+
* Writing and adapting NEON intrinsics.
105
+
* Identifying and fixing bugs in complex low-level code, even for developers who aren’t SIMD experts.
97
106
98
107
Make sure to try different LLMs with Copilot as the results will vary greatly depending on the model.
0 commit comments