Project stage 3 Integrate, Tidy, & Wrap

 The project code's location in class git repository should be under 
https://github.com/Seneca-CDOT/gcc/tree/2024-S-tests/gcc/testsuite/g%2B%2B.target/aarch64 
with folder name afmv, but its still waiting for review required approve.  
It is located in my branch waiting for the merge: 
https://github.com/zijunlii/gcc/tree/master/gcc/testsuite/g%2B%2B.target/aarch64/afmv
The directory structure is as follows:
gcc/testsuite/g++.target/aarch64/ 
└── afmv/ 
     ├── afmv_test_1.c 
     ├── afmv_test_1.exp 
     ├── afmv_test_2.c 
     ├── afmv_test_2.exp 
     ├── afmv_test_3.c 
     ├── afmv_test_3.exp 
     └── Makefile

The AFMV capability correctly creates and executes multiple versions of functions. Only basic functionality is verified. More complex functions will require further fixing and testing. 

Working on the AFMV project within the GCC framework has been an enriching experience. This project provided a deep dive into compiler design and optimization techniques, which are critical for modern software development. By integrating AFMV into GCC, I learned the importance of creating multiple optimized versions of functions to leverage various processor features, ultimately enhancing performance. The process of navigating GCC's extensive codebase, understanding its build system, and making meaningful contributions was challenging. 

Throughout this project, I encountered several challenges that significantly contributed to my learning. Building GCC from source and configuring the development environment required attention to detail and patience, highlighting the complexities involved in software projects. Debugging test failures and ensuring that the AFMV implementation worked correctly across different scenarios provided valuable insights into the importance of thorough testing and validation.

Comments

Post a Comment

Popular posts from this blog

Project stage 1 GCC build

This is the project stage 1, we will become familiar with the GCC build process on AArch86 and x86 platforms.  1. Clone the GCC repository from the official source git clone git://gcc.gnu.org/git/gcc.git cd gcc For AArch86 2. Creating build directory and configure GCC for AArch64 mkdir build-aarch64 cd build-aarch64 ../configure --target=aarch64-linux-gnu --prefix=$HOME/gcc-aarch64 --disable-multilib 3. Starting the build process and install GCC  make -j$(nproc) make install For x86 2. Creating build directory and configure GCC for x86 mkdir build-x86 cd build-x86 ../configure --prefix=$HOME/gcc-x86 --disable-multilib 3. Starting the build process and install GCC make -j$(nproc) make install While working on this project I leanred the build process and the necessary configurations for different architectures. The challenges was dealing with build dependenicies and managing long build times.
Read more

lab 1 mob programming

In this lab our focus was on the 6502 Emulator, a tool that simulates the classic 6502 microprocessor. The task involved filling a bitmapped display with different colors and optimizing the performance of the code. This blog post will outline our experiments, performance calculations, code modifications, and personal reflections on the process. Initial Code:  lda #$00    ; set a pointer in memory location $40 to point to $0200 sta $40     ; ... low byte ($00) goes in address $40 lda #$02     sta $41     ; ... high byte ($02) goes into address $41 lda #$07    ; colour number ldy #$00    ; set index to 0 loop:   sta ($40),y  ; set pixel colour at the address (pointer)+Y     iny     ; increment index     bne loop    ; continue until done the page (256 pixels)     inc $41     ; increment the page     ldx $41  ...
Read more