Project Stage 2

Firstly I created a custom pass code

#include "config.h"
#include "system.h"
#include "coretypes.h"
#include "backend.h"
#include "tree-pass.h"
#include "gimple.h"

namespace {
  const pass_data pass_data_afmv_diagnostics = {
    GIMPLE_PASS,      
    "afmv_diag",      
    OPTGROUP_NONE,    
    TV_NONE,         
    0,                
    0,                
    0,                
    0,                
    0                 
  };

  class pass_afmv_diagnostics : public gimple_opt_pass {
  public:
    pass_afmv_diagnostics(gcc::context *ctxt)
      : gimple_opt_pass(pass_data_afmv_diagnostics, ctxt) {}

    bool gate(function*) final override {
      return true;
    }

    unsigned int execute(function*) final override {
      fprintf(stderr, "AFMV Diagnostics: Hello, World!\n");
      return 0;
    }
  };
}

gimple_opt_pass* make_pass_afmv_diagnostics(gcc::context *ctxt) {
  return new pass_afmv_diagnostics(ctxt);
}

Register the Pass in passes.def
Edit passes.def to register the pass:
nano ~/gcc/gcc/passes.def

added this line:

NEXT_PASS (make_pass_afmv_diagnostics);

Declare the Prototype in tree-pass.h
Edit tree-pass.h to declare the prototype:
nano ~/gcc/gcc/tree-pass.h

Add the prototype:

extern gimple_opt_pass* make_pass_afmv_diagnostics(gcc::context *ctxt);


Include in Makefile.in
Edit Makefile.in to include afmv-diagnostics.o in the OBJS variable:
nano ~/gcc/gcc/Makefile.in

Add 
afmv-diagnostics.o

For now when I am trying to rebuild the gcc-build-001, 
I'm receiving some gimple check errors. 
I am trying to resolve this issues to complete Project Stage 2

Errors:
/libdecnumber -I../../gcc/gcc/../libdecnumber/bid -I../libdecnumber -I../../gcc/gcc/../libbacktrace -o c-family/c-ppoutput.o -MT c-family/c-ppoutput.o -MMD -MP -MF c-family/.deps/c-ppoutput.TPo ../../gcc/gcc/c-family/c-ppoutput.cc make[3]: *** [Makefile:1199: c-family/c-gimplify.o] Error 1 make[3]: *** Waiting for unfinished jobs.... Shared 73054 out of 134112 states by creating 11963 new states, saving 61091 /bin/sh ../../gcc/gcc/../move-if-change tmp-recog.cc insn-recog.cc echo timestamp > s-recog /bin/sh ../../gcc/gcc/../move-if-change tmp-output.cc insn-output.cc echo timestamp > s-output /bin/sh ../../gcc/gcc/../move-if-change tmp-automata.cc insn-automata.cc echo timestamp > s-automata /bin/sh ../../gcc/gcc/../move-if-change tmp-attrtab.cc insn-attrtab.cc /bin/sh ../../gcc/gcc/../move-if-change tmp-dfatab.cc insn-dfatab.cc /bin/sh ../../gcc/gcc/../move-if-change tmp-latencytab.cc insn-latencytab.cc echo timestamp > s-attrtab make[3]: Leaving directory '/home/ahryhorzhevskyi/gcc-build-new/gcc' make[2]: *** [Makefile:5057: all-stage1-gcc] Error 2 make[2]: Leaving directory '/home/ahryhorzhevskyi/gcc-build-new' make[1]: *** [Makefile:25283: stage1-bubble] Error 2 make[1]: Leaving directory '/home/ahryhorzhevskyi/gcc-build-new' make: *** [Makefile:1103: all] Error 2

Комментарии

Отправить комментарий

Популярные сообщения из этого блога

Project Stage 1

Изображение
Project Stage 1  Introduction to Configuring and Building GCC for AArch64 Setting up a local installation of GCC is the first step before delving into the finer points of the GCC codebase. The official installation instructions can be found here, but I've included a condensed version of the steps below. Copying the Source Code Clone the GCC source code repository in order to get started. Using an open terminal, type the following command: git  clone  git://gcc.gnu.org/git/gcc.git Setting Up the Build Directory It's important to create separate directories for different builds to maintain a clean and organized workflow. Execute the following commands to create and navigate to your build directory: mkdir ./gcc-build-001 cd ./gcc-build-001 Configuring the Local Installation In your new build directory, configure the build process by specifying a custom installation path. Replace  /path/to/install/gcc  with your desired installation location: ~/gcc/configure --pre...
Далее...

Lab01

Изображение
Lab 1:  Introduction Welcome to the first lab of our assembly language course, where we'll delve into the world of Mob Programming using the 6502 Emulator. Mob Programming is an extended form of Pair Programming, allowing a group to collaborate on coding tasks with designated roles like Driver and Presenter. This collaborative approach enhances problem-solving and knowledge sharing among group members. In this lab, we'll explore filling a bitmapped display with colour and optimizing code performance in assembly language. Setting Up Open the 6502 Emulator  at  6502 Emulator  in another tab or window. Save your work periodically  as the emulator does not auto-save. Use methods like copying code to a local file or using Git for version control. Bitmap Code We'll start by filling the emulator's bitmapped display with the color yellow using the following code: assembly Copy code lda #$00 ; set a pointer in memory location $40 to point to $0200 sta $40 ; ... lo...
Далее...

Lab 3

  Lab 3 Getting Started: Unpacking the Examples To begin, I unpacked the provided example files on the SPO600 servers: cd ~ tar xvf /public/spo600-assembler-lab-examples.tgz This produced the following directory structure: spo600 └── examples └── hello ├── assembler │ ├── aarch64 │ │ ├── hello.s │ │ └── Makefile │ ├── Makefile │ └── x86_64 │ ├── hello-gas.s │ ├── hello-nasm.s │ └── Makefile └── c ├── hello2.c ├── hello3.c ├── hello.c └── Makefile I first built and ran the C versions of the "Hello World" program: cd ~/spo600/examples/hello/c make ./hello ./hello2 ./hello3 Next, I used  objdump  to disassemble the binaries and inspect the  <main>  section: objdump -d hello objdump -d hello2 objdump -d hello3 I navigated to the x86_64 directory to review and build the assembly language programs: ...
Далее...