Project Part - 1

-

 The Goal of this project is as follow:

"The goal for this project is to produce a proof-of-concept tool that will take code that meets specific conditions and automatically build it with ifunc capability to select between multiple, autovectorized versions of a function, to take advantage of the best SIMD implementation available on the CPU on which the code is running." (Chris Tyler)

Project Part 1

To work with the main function and function file I am going to used C or C++ language as the base language. And Visual Studio Code as IDE for writing and impelling the test that is provide by our professor as follow : https://github.com/ctyler/spo600-fall2022-project-test-code

Overall Project Working :

1) Get Input from Keyboard when run.

2) Running the parameters successfully.

3) The solution of the file should be capable of changing parameters of file inside it.

4) No bugs should be there and the file can change at any moment.

SOLUTION :

I plan to add ifunc function in C code to get my solution 

1) Has the three inbuilt function which is going to implement.

2) Can build any kind to solution which is going to be excepted.

3) Successful get output of the code.

4) Number of output can be obtain with changing the input in the solution.

CHALLENGE :

  • My aarch64 system still has a few bugs as it nears completion. The test environment needs to be stabilised, thus further effort is required.
  • I might have to spend a lot of time googling the issues you experience on Arm devices.I need more time to find a solution because I don't feel particularly comfortable writing SIMD, SVE, and SVE2 C functions three times.
  • I choose to utilise ifunc in my C source code, but ifunc might not perform properly. You must use the guide to resolve this issue.
I'm still learning how to code this project step-by-step, and I need to do more research to understand how to accept arguments and adapt to arch64. However, we want to use GitHub to track updates, rollbacks, and code maintenance.

Comments

Post a Comment

Popular posts from this blog

ifunc function

-
IFUNC What is IFUNC? With the aid of a resolver function that was also written by the developer, numerous implementations of a particular function can be created using the GNU indirect function support (IFUNC) feature of the GNU toolchain. During early startup, the dynamic loader calls the resolver function to determine which implementation the application will use. Once a decision on implementation is made, it cannot be modified for the duration of the procedure. How to use it? As you can see, there are already a few limitations on how IFUNC can be used.                                                             It is t he implementations and the resolver must both be defined in the same translation unit. functions that cannot be weakly specified.    Since the resolution of an IFUNC might occur very early in the dynamic loader startup process, especially if -Wl,z,now is used to generate the application, the limitations are actually stricter than this (requires all symbols be resolved
Read more

Lab2 - 6502 Assembly Language Lab(Calculation)

-
Image
 In this lab we need to find how much is time need to complete the process of code. So here we need to find the number of the cycles that are need to complete the process of one line of code to processed. So as shown in photo  The load accumulator need two cycle to complete the process and only one time this code is run. After that store accumulator will run and same as load accumulator it will run ones with two cycle. After all the function will be run as shown above but when the loop will be there t process will be change there are 256 bytes in one page and there are total 4 page to this will run 12 time and as shown above it will be executed.  And the time will be 5935us when there was 1Mhz clock speed is there. To change the speed we need to make change like we need to change the loop of pages to only one  which can change the part of time but I am not able to make that one. 
Read more

Lab1 - 2 Open Sources Packages

-
Image
 Hello everyone here is my two open sources project that I am going to discuss are as follow : Firefox Brower and VLC player. Firefox Browser  The License that Firefox Brower has is MPL. MPL is Mozilla public  license. and under Mozilla with the current version of 2.0(html|plan text). Process for submitting an patch: Step 1  is every change to the code is tracked by a bug report in bugzilla.mozilla.org. Without a bug, code will not be reviewed, and without review, code will not be accepted. Step2 is the patch is going to be commit to the version control and every patch should be submitted in the single complete change, separating distinct changes into multiple individual patches. And check that commit message is there. Step3 is for testing the patch that has been reported. Most of the changes are done using automated test and the code is change. There is also a static analysis going on with JavaScript for the best practices and common mistakes. Step4 is to submit the patch. Mozilla use
Read more