Skip to main content

Just a Loop

Photo by Tine Ivanič on Unsplash
Hey everyone! This post is dedicated to Lab 5. I’ll say upfront that this was the most challenging loop of my career. Yes! If you told assembly, you were right. Our professor was kind to provide necessary codes from each platform. He also gave us access to several machines with different hardware capabilities for both architectures. Combined with the previous lecture, we had everything that we need to succeed.

The goal was to create a program that shows “loop” ten times. Next, we had to change it to include the index number. Finally, extend it to show thirty times with the index suppressing the leading zero. Don’t forget, on BOTH architectures! If it were on C, C++, Java, JavaScript or Bash, I would have time to a coffee.

To be fair, the first task was to put the “hello world” with the script provided. That was easy, and the only one that I accomplished. To compile it, I added a new target to the make file provided. The result you can see below.




The next is the indexed loop. Remembering the previous lecture, if we use a place holder in the message and change it before displaying, it would produce the desired output. Easy to say, hard to do it! I got stuck on how to change that little “X.” Even with my professor’s tip – use the binary move – I couldn’t figure it out. Hey Siri, could replace the X placeholder with the loop index, please? Siri just put some music on – Dammit, Blink-182! Here is the result of my failure.


The last challenge, I know some ways. We could use an “if” statement to see if the value is less than 10 to hide the leading zero. We could separate the index into two “variables” (one for decimals and the other for the units). However, I lack the knowledge of the language and the hardware to make it happen. Do I get some marks doing it in C or C++? Dammit is still playing in the background.

This is it! Epic failure and a great time playing with x86_64 and ARMv8. See you.
Labels:

Comments

Post a Comment

Popular posts from this blog

Going Faster

Photo by  Anders Jildén  on  Unsplash Today’s topic is compiler optimizations. Besides translating our source code into machine binary executable, the compiler, based on optimization parameters, can also produce faster executables. Just by adding some parameters to the compiler, we can get a better performance or a smaller executable, for example. There are hundreds of those parameters which we can turn on or off using the prefix -f and -fno. However, instead of doing one by one, we can use the features mode using the -O param. It ranges from 0 (no optimization – the default) to 3 (the highest). Using those parameters has a cost —usually, the faster, the larger executable. How does the compiler make it faster if my code is perfect? I’m going to put some methods here, but if you want, here is more detail . Also, bear in mind that most of the optimizations are done in the intermediate representation of the program. So, the examples below are rewritten just to...
Post a Comment
Read more

Project Stage 3

Photo by  NASA  on  Unsplash Hello! In this post, I’ll make a list of optimization opportunities that I identified on the AWK project based on what I’ve learned in the SPO600 classes. There are two types of optimizations: portable and platform-specific. Portable optimizations are the ones that work everywhere, like better algorithms and implementations, and also compiler building flags. Platform-specific, on the other hand, works only for a targeted architecture. Like the SIMD instructions available only on Arch64 and many others specific for x86_64. It is possible to “force” the usage of such instructions according to the targeted hardware. We can do that on compilation time, and also on run-time. Now that we know our options, let’s dig in. According to my previous post , the functions nematch and readrec are the hotspots. Here is the command line used to run the awk: ./awk 'BEGIN {FS = "<|:|=";} {if ($8 == "DDD>") a ++;} END {print "cou...
Post a Comment
Read more

Colour Selection

Photo by Scott Webb  on  Unsplash Today I'll talk about Lab 4. We had to pick two tasks out of four and develop the solution using my least favour language: assembly. Our group chose the options 2 (data input form) and 4 (screen colour selector) thinking that would be the easiest ones. The other options were adding calculator and hexdump. This post will talk about the colour selector, and my next will be the input form. The colour selector project was quite easy to do relatively. There are only 16 colours available (0 to F in hex). We have to list them in the text area and allow the selection using the cursor (up and down). Once the colour is selected, we have to paint the graph area. The graph area we did before. Basically, we have to store the colour code for every pixel in the display using the memory location between $0200 and $05FF. In the last post, we deal with up and down keys to change the numeric display. However, we never dealt with character display bef...
Post a Comment
Read more