Hello World in Assembly

Assembly alert! I promised to talk more about the compiler, but before it, more assembly. It is for a good reason, though. I was surprised to see my professor doing the “hello world” in assembly! Not only on x86_64 but also in the ARMv8 – different source code. He coded just like C or C++, saved, compiled and run it. The output was exactly like any other language. Nobody knew, but he was doing the Lab 5! I wish I were recording it.

Our goal in this class was to compare the compiler output with the hand-crafted assembly. As expected, the compiler produced non-optimal executables even when we played with some fine-tuning options that I mentioned in the last post.

How to compile an assembly code? Here are the commands:

- Using GNU Assembler
> as -g -o test.o test.s
> ld -o test test.o

- Using NASM Assembler
> nasm -g -f elf64 -o test.o test.s
> ld -o test test.o

- Using GCC
> gcc -g -o test.o test.S

How to get the assembly code from an executable?
> objdump -d test

Using those tools, we played on both architectures, and the compiler didn’t get any closer than our hand-crafted script. However, I don’t believe that we should start using low-level languages for everything. There are drawbacks to doing so. The major one is the fact that assembly is hardware-oriented. This means that it needs to be rewritten on different platforms. Comparing it with C or C++, you just need to code once and compile it multiple times (one for each platform). So, unless it is a requirement, I would take it as a last resource to improve the performance.

If you want to know more about the used scripts and the assembly language, here are some resources:
https://wiki.cdot.senecacollege.ca/wiki/Assembler_Basics
https://wiki.cdot.senecacollege.ca/wiki/SPO600_64-bit_Assembler_Lab

See you!

Comments

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...

Data Input Form

Photo by Marvin Meyer on Unsplash Continuing the Lab 4, we are going to develop the option 2, data input form. The goal is to prompt the user to enter its name, address, city, province and postal code. Also, letting the user use up, down, left, and right arrows to navigate throughout the fields. After finishing the data input, a summary is presented at the end. Using the ROM routines, wasn’t too hard to allow users to type data into the character display. Then, I decided to make the filed names with the same width, 14 characters, limiting the input to 40 characters. So, the user is not allowed to type in the first 14 and after 54 characters. When the user presses enter at the last field, the summary is shown. I could display the fixed message, but I couldn’t copy the inserted data. I’m still working on that, and I’ll update this post as soon I figure it out. It is frustrating for me to spend days in basic problems that could be solved quickly using other langu...

Two-digit Numeric Display - Final

Photo by Nick Hillier on Unsplash In this post, I’ll continue the two-digit numeric display. If you miss it, click here and check it out . To finish this project, we just need to show the numbers in the matrix-pixel (the black-box in the 6502 emulator ). To kickstart, our instructor gave us one example of how to display graphs, which was a lot helpful. The first thing that I’ve noticed was the bitmap table at the bottom. So, I mimic it and made ten tables like that to represent each number (zero to nine). So far, so good! Then I grabbed the logic to display one digit, and then my nightmares just started. How to place two graphs (one for each digit)? How to switch from one number to another? How to reuse code? Where is my coffee?! To emulate some if-elseif-else statements, I used jmp (jump). They are all over the place! However, the 6502 limits the jump range from -127 to 128. That means moving the code-blocks to satisfy all jumps limit. For e...

Rodrigo

Search This Blog