Project Stage 3

Goal:
 

After checking if the options are valid. Have to create a global array of afmv_targets and unsigned int of afmv_cnt. This is for others to consume.

-fafmv="default" will have a count of 0.

-fafmv="default, abc" will have a count of 1.

Try to use the target_clone in GCC.

Make a afmv.h for the global var I have to make.

Header file:
#ifndef GCC_AFMV_H
#define GCC_AFMV_H

/* Storage global variable for AFMV*/

#define AFMV_MAX_ARRAY_SIZE 100

extern unsigned int afmv_cnt;
extern char* afmv_targets[AFMV_MAX_ARRAY_SIZE];

#endif /* GCC_AFMV_H */


add include header in opts.cc

update count and array if all options passes the chceck.

unsigned int afmv_cnt = 0;
char* afmv_targets[AFMV_MAX_ARRAY_SIZE];

and
    if (!is_found) {
        error_at(loc, "Unsupported option '%s'", feature);
        is_valid = false;
    } else {
        afmv_targets[afmv_cnt++] = feature;
    }

at the end:
afmv_cnt--;

Becuase we want to set default as 0.

I am not sure if there will be any memory leak if i do it this way. I couldn't use the build in clone features to identify if the options are valid. I am using a hard coded arr for comparing.

Here is a link to my gcc Fork: https://github.com/Pulse6/gcc-command-line-parsing/tree/2024-S-command-line-parsing 

Conclusion:

    My task is to work with the current code base in GCC. It was hard to learn where things are at first because of it's huge code base, also we have a very limited time to learn and research to get to our goals. I have gain some knowledge of "make" and "make install" a version of GCC that I can modified. It is a similar concept to GIT, just for a version control. It is cool that makefile can re-build a version of your modified code and is able to know what I change and base on that it can only update and build the affected files. It is crazy to me that how much knowledge those who maintain the GCC code base. The little task I have to do for me is already overwhelming, but it is just a tiny part of GCC.

    I have to find where do GCC takes in the command and where does it go. Also got to try follow the guideline of GCC. Used google to try to get some information of that. Went back to class recordings to get more out of it. Thankfully professor take the time to explain every task in details. Gives us a more clear path to go on.

    This is also the first time I have work with a community GitHub project. First time doing forks of projects and making a pull request. That idea is also fun too. At the beginning of doing this task backs me back when i just started learning C is was so new and i have no idea what's going on, but if i keep on going to gets better. I did the same on this class/project. The sad part of this course is they made it in to a 7 week course. The course itself is already hard, and they make it half the time. However Chris our professor is a great teacher and make it much better to go through.

 

 

 

 

 

 

 

 

Comments

Post a Comment

Popular posts from this blog

Lab 1

Image
Introduction Starter 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 ; get the current page number cpx #$06 ; compare with 6 bne loop ; continue until done all pages Open the 6502 Emulator at http://6502.cdot.systems paste the starter code in the input box. Click Assemble and Run to see results. Calculating Performance     cycles count alt-cycles alt-count total     lda #$00 2 1     2     sta $40 3 1     3     lda #$02 2 1 ...
Read more

Project Stage 1

GCC install and build with version Before diving into the code, let's set up a local GCC installation. Head over to the official installation guide https://gcc.gnu.org/install/ for detailed instructions. Here's a quick rundown: Clone the Source: Use git clone git://gcc.gnu.org/git/gcc.git to grab the latest GCC source code. Build Directory: Create a directory "mkdir" for your build and navigate to it using "cd" . you can create different versions for different use case, but keep in mind GCC is not small. Once you are done with the build, you can simply delete the build files . We create different directory for different build so it would have a cleaner workflow. mkdir ./gcc-build-001 cd ./gcc-build-001 Local Installation: In your newly made build folder. Specify a custom installation path with "../configure --prefix=/path/to/install/gcc ". Replace "/path/to/install/gcc " with your desired location. This will create a make file fo...
Read more

Project Stage 2

 My task is: Command-line Parsing Description: Parse the GCC command line to pick up AFMV options, process the version list to validate the architectural feature specification. (example: -fafmv=var1,var2) One of the places to see how others did it is on GitHub of other class that did similar project task. I could also go on GCC's git to see pass commit that is could be related to my task of adding a pass. Most of my work will be done in the  .opt file writing. We will be using slack as a communication tool. Link: other class: https://github.com/seneca-cdot/gcc GCC: https://gcc.gnu.org/onlinedocs/gccint/ GitHub: https://github.com/seneca-cdot/gcc (I work in the branch " 2024-S-command-line-parsing ") GitHub branch: https://github.com/Seneca-CDOT/gcc/tree/2024-S-command-line-parsing I will be using the class server. I don think I want to spend time on trying to do it on my local device. This term of SPO600 they cut the time in half. We are very time limited. This stage we...
Read more