Planet Chili

Contiguous storage has become more in favour nowadays. It's better to allocate a huge chunk of memory to store all your objects in over allocating seperate chunks of memory for each object. The main reason comes from one aspect of modern CPUs: caching . CPUs are so fast at calculations that retriev...

x86 refers to the instruction set that the Intel and AMD processors use. It's named after the Intel 8086 processor which is the processor that the instruction set is based on. It is actually not directly tied to 32bit processing as the 8086 processor was actually 16 bits back then. The 64bit extensi...

The typename keyword is because of 2 phase lookups that templates go through. Before the template can be fully checked for errors in the second phase where the type parameters are given, it does a quick syntax error check in the first phase with the template itself without any known type parameters....

Looks like you didn't install the right modules. Try reinstalling again to install all the C++ Windows development modules.

Morning class! Today, we'll be going into the fun things you can do with templates! Now even though Chili has already covered the basics of templates, the world of template metaprogramming is far more vast than one video can cover! Today, we are going to explore ways templates can simplify code thro...

I decided to take the next step and see if a multi threaded implementation would work better. Multi threading became more popular as people realized that it can be used to work around i/o stalls. If a thread stalls because of i/o, the cpu can just run another thread instead. It failed...horribly. :l...

About pipelining: Out of Order execution optimizes the pipelining process a little bit further. Generally, an OoO processor works as such: 1)Instruction is fetched. 2)Instruction is stored in an instruction buffer. 3)Instruction waits in the buffer until its inputs are available in the register. The...

Approach 1: int a = 2; int b = 5; int c = a + b; unit[0].doSomething( c ); unit[1].doSomething( c ); Approach 2: unit[0].doSomething( a + b ); unit[1].doSomething( a + b ); Interesting. If these functions are inlined, it's better to do calculations first since the values would stay in the registers...

So here's an example some of you would've run into at one point. Say you have a bunch of planes. These planes can shoot missiles at each other. The missiles themselves are homing meaning that it can track its target and move towards it. For some of us, we would represent their data structure as such...

The ballista is just outright more powerful than the bomber. Although the bomber might be able to one shot enemies, its slow re-fire rate plus limited range usually means that enemies will escape it before it has the chance to shoot. Ballistas are cheaper too so you can just spam those and win throu...