We’ve been having so much fun, we haven’t written any benchmarks! Though it isn’t the most exciting thing to write, they are important. == Benchmarks There’s two things to understand about benchmarks:
Hello! In this part, we’re going to factor out the command parsing done in the REPL for user input. Right now, there isn’t much flexibility; a user cannot type:
If you’ve been following the development of Iridium, you know how heavily it uses
Nom to parse the assembly language. I hope you liked it, because we’re going to be using
Nom for this as well. =)
In this tutorial, we’re going to start creating a language called
Palladium that will compile down to the assembly code we’ve been using.
Before we get started, please remember…
Hey everyone! In this tutorial, we’ll add PID tracking to the Iridium VM. Please ensure you are starting from https://gitlab.com/subnetzero/iridium/tags/0.0.17. == PIDs There are two components we need to unique identify:
Hello! This article discusses the two types of scaling found in infrastructure. These concepts aren’t extra-mysterious or anything; there are some subtleties to them that can trip you up.
Hey everyone! This is a short article on concurrency, parallelism, and the differences between the two.
Hey everyone! In this tutorial, we’re going to start adding in multithreading to the Iridium VM. Please make sure you are starting from this point in the code: https://gitlab.com/subnetzero/iridium/tags/0.0.16. Going forward, I’m going to make a tag per tutorial so that everyone starts from a common point. === A Note on Assumed Knowledge I write these tutorials target towards more advanced users. I sometimes skip small steps, such as "add in this line to file X".
This is going to be a longer post. In it, we’ll wrap up our two-pass assembler, add a
PRTS opcode for printing, and tie up some other loose ends. At the end, we should have an interpreter with a good amount of functionality and a simple assembly language. We are, of course, far from done with the project. I want to work on a different tutorial series for a bit, then we’ll continue with Iridium.
=== Quick Change
Add the following dependencies in your Cargo.toml. We’ll need them later:
Having to start the interpreter, then type
.load_file, etc is cumbersome. Let’s change it so that the VM tries to execute the file given to it as an argument. There’s a super handy-dandy crate called
clap in Rust that will make this trivial. The behavior we want is: